Comments
Sort by recent activity
Thanks for your post.
Using the /include switch should do what you need. Only the tables stated in the /include will be used in the project.
What happened when you tried this?
Another thing you might like to try is using SQL Source Control 2.0. We currently have an early access release of this product, which will allow you to source control static data directly from SSMS. / comments
Thanks for your post.
Using the /include switch should do what you need. Only the tables stated in the /include will be used in the project.
What happened when you tried this?
Another thing you mig...
Thanks for your post.
I think the reason you can't sync a view with an identity column, is because you can't SET IDENTITY INSERT ON when updating a view. It reality though, it's pretty unlikely that you will be able to sync a view anyway, because it will only work if a view only references a single table. If a view references more than one table you'll get an error about not being to update multiple base tables.
With regards to sync'ing identity columns, if you set the option to include identity columns, then SQL Data Compare will SET IDENTITY INSERT ON and then insert the identity's on the target exactly as they are on the source. If you don't include identity, then the script will probably allow the server to assign the identity value when inserted, or leave it alone if the row already exists.
You can probably see what's happening if you check the script before you synchronize.
I hope this helps. / comments
Thanks for your post.
I think the reason you can't sync a view with an identity column, is because you can't SET IDENTITY INSERT ON when updating a view. It reality though, it's pretty unlikely tha...
Thanks for your post.
When the sync fails, you should get error 126 returned. It's a bit strange you're getting 0.
What happens when you run the command through the command prompt rather than an SSIS package?
What does it say in the redirected console output? (c:\temp\%1_%2.txt) / comments
Thanks for your post.
When the sync fails, you should get error 126 returned. It's a bit strange you're getting 0.
What happens when you run the command through the command prompt rather than an SS...
Thanks for your reply.
I edited your last post to remove your serial number.
It looks like the windows account you're using for the comparison can't be authenticated. Are you able to log into both servers with SSMS using that account?
You could try using a SQL Account for each database, e.g. /username1:sa /Password1:mypassword /username2:sa /username2:mypassword / comments
Thanks for your reply.
I edited your last post to remove your serial number.
It looks like the windows account you're using for the comparison can't be authenticated. Are you able to log into both ...
Thanks for your post.
Have you tried reinstalling SQL Data Compare? If it works on another machine, then as you suspect, it must be environmental.
I would also suggest trying the patch version available here / comments
Thanks for your post.
Have you tried reinstalling SQL Data Compare? If it works on another machine, then as you suspect, it must be environmental.
I would also suggest trying the patch version avai...
Not any good ones....
Do you get the same problem if you use the command line switches rather than calling a project file? e.g.
C:\Documents and Settings\adrianda>"C:\Program Files\Red Gate\SQL Data Compare 8\SQLDataCompare"/db1:SourceDb /db2:Targetdb / comments
Not any good ones....
Do you get the same problem if you use the command line switches rather than calling a project file? e.g.
C:\Documents and Settings\adrianda>"C:\Program Files\Red Gate\SQL Dat...
Thanks for posting.
We've reproduced this issue in tests now, so we should have a fix fairly soon. / comments
Thanks for posting.
We've reproduced this issue in tests now, so we should have a fix fairly soon.
Thanks for your post.
I believe this issue only occurs when using the 'split transactions' option.
It should be fixed in the latest cumulative patch, found here
This fix isn't mentioned in the list of fixes, but that's only because it was originally reported as a SQL Packager problem. (SQL Packager uses the SQL Data Compare engine for the data part) / comments
Thanks for your post.
I believe this issue only occurs when using the 'split transactions' option.
It should be fixed in the latest cumulative patch, found here
This fix isn't mentioned in the list...
Thanks for your post.
What are the symptoms of the server being crushed? Is SQL Server causing very high CPU or memory usage, or is the SQL Compare process consuming all the resources?
Does the procedure wait for the previous EXEC (@CMD) to complete before it starts the next one, or are multiple instances of SQL Compare being opened?
Usually SQL Compare will be run from a workstation and not on the server itself. If SQL compare is causing the problems on the server, you could try running SQL Compare on a different machine.
I hope this helps. / comments
Thanks for your post.
What are the symptoms of the server being crushed? Is SQL Server causing very high CPU or memory usage, or is the SQL Compare process consuming all the resources?
Does the pro...
Thanks for your post.
As you have found, the only current workaround for this is to use the scripts tab and disable the FK relationship yourself before you insert the data. I believe the thinking was that if you're going to generate data for a table with a FK relationship, that you would also want to generate data for the FK table too.
There are a few situations where this isn't always the case, and those situations are not easy to deal with using SQL Data Generator.
We have an open feature request the allow the disabling of foreign keys, similar to SQL Data Compare. With this feature we will have to trust that the user will not generate data in such as way to make the FK invalid when it is enabled at the end. Anyway, I have added you as another vote for SDG-900.
With regards to the triggers query. We have the project option to fire Insert or Delete triggers, so I assume if these options are unchecked that the triggers will not fire when you insert or delete. / comments
Thanks for your post.
As you have found, the only current workaround for this is to use the scripts tab and disable the FK relationship yourself before you insert the data. I believe the thinking w...