Comments
Sort by recent activity
Thank you! I've been using SQL compare for years and never knew you could do that... I just figured it came with the last update I installed. / comments
Thank you! I've been using SQL compare for years and never knew you could do that... I just figured it came with the last update I installed.
This was actually resolved in the latest frequent updates. See this thread: viewtopic.php?f=177&t=79113 / comments
This was actually resolved in the latest frequent updates. See this thread: viewtopic.php?f=177&t=79113
Fixed! Thank you very much! I almost cried a little when I thought I wouldn't be able to use SQL compare anymore. [image]
-Ben / comments
Fixed! Thank you very much! I almost cried a little when I thought I wouldn't be able to use SQL compare anymore.
-Ben
Did you ever get any answer to this? I just started at a company that uses a 3rd party encryption and am having a similar issue. I can't even snapshot a database... / comments
Did you ever get any answer to this? I just started at a company that uses a 3rd party encryption and am having a similar issue. I can't even snapshot a database...
Did you ever get a solution to this? I have the same issue with any partition function that uses a nonstandard DATETIME2 type, in my case, I use DATETIME2(2) all over the place.
To get around this, I have to drop the offending functions/schemas and all tables that use it. Link the database and get latest, re-add all the tables schemas and commit everything but the PF and PS. Manually commit PF and PS into TFS.
Every time I go to commit after this, it works, but it shows the PF and PS as needing to be commited. It never actually commits it even if you select it or not. This has been a bug for a long time and i've submitted several error reports.
I keep hoping they fix it when i update SQL source control, but it has yet to happen.... / comments
Did you ever get a solution to this? I have the same issue with any partition function that uses a nonstandard DATETIME2 type, in my case, I use DATETIME2(2) all over the place.
To get around this...