Comments
Sort by recent activity
Update - I can get this to happen on my current v2 build as well.
I've raised a bug for this under reference SOC-2071 as I couldn't see it already listed as an issue, but if that changes I'll let you know.
Not sure of a workaround as yet unfortunately. / comments
Update - I can get this to happen on my current v2 build as well.
I've raised a bug for this under reference SOC-2071 as I couldn't see it already listed as an issue, but if that changes I'll let y...
Thanks for your post. I'll see if I can replicate it here myself. Did you submit an error report when the problem occurred? If you do this, it should tie it in to any other occurrences of that particular problem in our database here. / comments
Thanks for your post. I'll see if I can replicate it here myself. Did you submit an error report when the problem occurred? If you do this, it should tie it in to any other occurrences of that part...
Thanks for the example. I see what you mean now.
On checking here, I can see we have a change-request logged that raises a similar point, so I will add the details of this post to that.
I'm not sure when that's likely to be implemented unfortunately but for now it looks like there isn't a way around the problem. / comments
Thanks for the example. I see what you mean now.
On checking here, I can see we have a change-request logged that raises a similar point, so I will add the details of this post to that.
I'm not sur...
I don't think there are any options that would really affect this. Can I first get you to check you're using the latest patch in case it helps? You'll find that in this post - if that doesn't help could you maybe post / email to support a create script for the object in question so we can try to replicate the problem? / comments
I don't think there are any options that would really affect this. Can I first get you to check you're using the latest patch in case it helps? You'll find that in this post - if that doesn't help ...
Hi,
The ignore constraint names option only affects the comparison stage, not the synchronization stage. So by ticking it, it won't flag objects as being different if the constraint name is the only difference, but if you have other diffs (such as a new column) then the constraints will be included when you sync.
So really, the recommendation would be to name your constraints yourself rather than letting SQL create the names, as these will be different every time. / comments
Hi,
The ignore constraint names option only affects the comparison stage, not the synchronization stage. So by ticking it, it won't flag objects as being different if the constraint name is the onl...
Afraid so - hope it's not too much of a headache! / comments
Afraid so - hope it's not too much of a headache!
Thanks for that - hopefully other users who would like to see this implemented will add their vote [image] / comments
Thanks for that - hopefully other users who would like to see this implemented will add their vote
Thanks for your post.
Unfortunately at the moment we don't support retrieving the history for objects that have been moved like this.
Because Tortoise can do it (with the tick-box you mention) it is possible we could add this in the future. Could I ask you to add it as a request on our uservoice forum for Source Control? You'll find it here
If plenty of other users vote up this option, it will get considered for inclusion in a future release. / comments
Thanks for your post.
Unfortunately at the moment we don't support retrieving the history for objects that have been moved like this.
Because Tortoise can do it (with the tick-box you mention) it i...
Thanks for your post. I've found a couple of instances of similar messages from other posts and supportcalls. There is a post here: http://www.red-gate.com/messageboard/vi ... php?t=5803 which details a registry key you can put in to increase the timeout on the checksum query (from what I gather, it still needs to go under the Compare 5 section) which may help.
I'm not sure why it would run ok from the commandline directly as opposed to a SQL Job, unless SQL Server somehow treats processes started as a SQL Job differently.
If the registry key doesn't help, perhaps try downloading a trial of version 8 to see if the problem persists, as I don't see any recent reports of this particular message. / comments
Thanks for your post. I've found a couple of instances of similar messages from other posts and supportcalls. There is a post here: http://www.red-gate.com/messageboard/vi ... php?t=5803 which deta...
Just following on from my previous post- you can compare source-controlled versions although it's a more manual process.
The steps would involve you using your command-line source control tools to grab a copy of both the source and destination sets of folders to work with, and then using SQL Compare via the command line. We have a white paper here which has an example using SVN, which may be of interest. / comments
Just following on from my previous post- you can compare source-controlled versions although it's a more manual process.
The steps would involve you using your command-line source control tools to ...