Comments
Sort by recent activity
Thanks for your post.
There isn't a huge amount of support for replicated databases, but there are a few project options that might help.
Have you tried the ignore options:
'NOT FOR REPLICATION'
'Replicationtriggers'
I have added this post as another vote to support replication properly in a future version. The feature tracking code for this is SC-2437.
If you have more specific problems that these options don't address, then you might be able to manually edit the script to get round them, but other then filtering out the objects, there isn't anything built into the tool you could use. / comments
Thanks for your post.
There isn't a huge amount of support for replicated databases, but there are a few project options that might help.
Have you tried the ignore options:
'NOT FOR REPLICATION'
'R...
Thanks for the suggestion.
It seems like a useful addition, so I have logged the request for the product managers to review.
Hopefully it will be considered for a future version of SQL Data compare.
For your reference the feature tracking code is SDC-1158. / comments
Thanks for the suggestion.
It seems like a useful addition, so I have logged the request for the product managers to review.
Hopefully it will be considered for a future version of SQL Data compare...
Thanks for your post.
I believe the reason you're getting this error is because by default, SQL Compare will script the transaction isolation level to be read committed, this causes problems with linked servers. If you manually change the script to:
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
Then it should probably be fine.
We have a feature request already in place and hope to resolve this issue with linked servers in a future version. (SC-1318).
I hope this helps. / comments
Thanks for your post.
I believe the reason you're getting this error is because by default, SQL Compare will script the transaction isolation level to be read committed, this causes problems with l...
Thanks for your post.
I haven't seen this happen before, so I can't give you much advice.
Is there any chance you could send me the script for the stored procedure so I can try and recreate this? Can you either post the script here or reply to the support ticket we opened for you? / comments
Thanks for your post.
I haven't seen this happen before, so I can't give you much advice.
Is there any chance you could send me the script for the stored procedure so I can try and recreate this? C...
Looking into this a bit further, we already have a feature request open for this.
If you would like to see support for these keywords, then please vote for the feature here / comments
Looking into this a bit further, we already have a feature request open for this.
If you would like to see support for these keywords, then please vote for the feature here
Thanks for your post.
That would be the way I would recommend to do it. Although identical records will excluded from the synchronization by default. / comments
Thanks for your post.
That would be the way I would recommend to do it. Although identical records will excluded from the synchronization by default.
Sorry for the slow response. We only just noticed you are still waiting for a reply to this, so thanks for your patience.
There isn't an easy way to distribute the link configurations with your team. You can find the information about the links in the Linkeddatabases.xml file in your user profile, but the settings are specific to each user so they can't easily be shared.
Unfortunately, each user will need to set this up themselves, but they should only have to do it once.
Also, it isn't recommended to link your production database with SQL Source control. If you need to make production changes, it will be better to deploy the changes using SQL Compare.
I hope this helps. / comments
Sorry for the slow response. We only just noticed you are still waiting for a reply to this, so thanks for your patience.
There isn't an easy way to distribute the link configurations with your tea...
Thanks for your reply.
I'm afraid SQL Compare doesn't compare the database level collation, only the object level collation.
If you don't want to make the column level collation the same in the source and the target, the only option is to ignore them completely.
If you ignore the collation and a new object is created, SQL Server will use the database default collation for the column. / comments
Thanks for your reply.
I'm afraid SQL Compare doesn't compare the database level collation, only the object level collation.
If you don't want to make the column level collation the same in the sou...
Thanks for your post.
Have you tried the project option 'Ignore Collations'? It sounds like it should do what you need.
Edit Project > Options > Ignore > Collations
I hope this helps. / comments
Thanks for your post.
Have you tried the project option 'Ignore Collations'? It sounds like it should do what you need.
Edit Project > Options > Ignore > Collations
I hope this helps.
Thanks for your post.
I've just tried to recreate this and I was able to use both /scriptfile and /sync together.
Did you set the /force switch so that you can overwrite the existing script file?
If this doesn't help, can you post the command you are using? / comments
Thanks for your post.
I've just tried to recreate this and I was able to use both /scriptfile and /sync together.
Did you set the /force switch so that you can overwrite the existing script file?
I...