Comments
Sort by recent activity
Thanks for your post.
I believe this has been fixed in the latest patch release.
SDC-1039 Can not Maximise Project Configuration
Could you try installing the patch and see if it fixes the issue?
You can download it from here
I hope it helps. / comments
Thanks for your post.
I believe this has been fixed in the latest patch release.
SDC-1039 Can not Maximise Project Configuration
Could you try installing the patch and see if it fixes the issue?
Yo...
Thanks for your post.
You can exclude the assemblies from the synchronization by deselecting them from the comparison results, but you will probably also need to deselect all the other objects that have a dependency to the assemblies.
You can turn off the option to 'include dependencies' when you step through the synchronization wizard, but if you don't include all dependent objects then your script may fail.
SQL Compare should have correctly identified the dependency and created the correct script to make the change, so I'm not exactly sure why the dependency would have been missed.
If you would like us to look into it for you, would you be able to email me schema snapshots (created in SQL Compare) that I can use reproduce the problem? If you send the email to support@red-gate.com with F0032491 in the subject, it will update the ticket we have open for you.
I hope this helps. / comments
Thanks for your post.
You can exclude the assemblies from the synchronization by deselecting them from the comparison results, but you will probably also need to deselect all the other objects that...
Thanks for your post.
I'm not sure myself if this is a bug or a cruel trick, but it is a known issue (SC-4631).
Sorry for the annoyance, normal serivce will resume in a future version. / comments
Thanks for your post.
I'm not sure myself if this is a bug or a cruel trick, but it is a known issue (SC-4631).
Sorry for the annoyance, normal serivce will resume in a future version.
Thanks for your post.
When you run the same project through the UI, does it show differences?
Databases that are identical will show up as "Error: The selected objects are identical or no objects have been selected in the comparison." on the command line. / comments
Thanks for your post.
When you run the same project through the UI, does it show differences?
Databases that are identical will show up as "Error: The selected objects are identical or no objects h...
Thanks for your post.
I'm guessing that you already have an existing copy of DotNetNuke db on your local instance, and the problem is trying to overwrite your copy with the version in source control.
We should be able to handle this scenario with SQL Source control, but we currently have a few issues if users start off with an existing db.
Would you be able to send us the schema for your local and source controlled copy and we can see if we can spot the problem? You can take a schema snapshot of your local db with the following tool: http://labs.red-gate.com/index.php/Red_Gate_Snapper
Are you able to 'get latest' if you start off with a blank db and link to that?
If you need to keep the data, would you be able to use SQL Data Compare to populate the latest schema with the data from the old database.
If you can send us a zip with the files, please send to support@red-gate.com and mark it for the attention of Chris.
Thanks, / comments
Thanks for your post.
I'm guessing that you already have an existing copy of DotNetNuke db on your local instance, and the problem is trying to overwrite your copy with the version in source contro...
Thanks for the snapshot, I can see the problem now.
It looks like SQL Source control is failing bacuse it is trying to create role memberships with roles that haven't yet been created.
This is now logged as bug SOC-830 and will be look at by the development team.
You can workaround the problem for now by first retrieving only the roles, and then retrieve all the other objects. Don't worry about resolving the conflicts until you have all the roles in your local db. Once you have the roles, you can resolve the conflicts and grab the rest of the objects.
I hope this helps. / comments
Thanks for the snapshot, I can see the problem now.
It looks like SQL Source control is failing bacuse it is trying to create role memberships with roles that haven't yet been created.
This is now ...
Thanks for your post.
Can I ask how you originally added the table without the collation to subversion? The reason I ask is because SQL Source control will include the column collation when it adds the new object.
There isn't currently an option to ignore the collations, but there isn't any reason why we couldn't add it to a future version if enough people would find it useful. / comments
Thanks for your post.
Can I ask how you originally added the table without the collation to subversion? The reason I ask is because SQL Source control will include the column collation when it adds...
Thanks for you post.
There is indeed a bug with the command line that causes this behaviour. The problem is that the UI filters out the indentical objects from the sync, but the CL doesn't. The artifact of having identical objects in the sync is that the sync script decides to refresh all the views.
You should have prevented this behaviour using the /exclude:Identical switch. However, we have another bug in the release version that makes /exclude:identical case sensitive.
Can you try the same command again, but use a lower case i in 'identical'?
We have a patch version that addresses this case sensitive issue that you can download from here
I hope this helps,
Let me know how you get on.
P.S. for your reference, the bug tracking number for the sp_refreshview issue is SC-4542. It should be fixed in the next release. / comments
Thanks for you post.
There is indeed a bug with the command line that causes this behaviour. The problem is that the UI filters out the indentical objects from the sync, but the CL doesn't. The art...
That feature's still there. It's on the right-click context menu.
'Show object Synchronization script' / comments
That feature's still there. It's on the right-click context menu.
'Show object Synchronization script'
Thanks for your post.
I think I might have managed to reproduce this now. It seems to happen pretty consistently when you try to include/exclude specific rows from the sync.
It's now logged under the bug tracking code SDC-1118. Hopefully we will write a fix for it soon.
I'll let you know as soon as I have some more information. / comments
Thanks for your post.
I think I might have managed to reproduce this now. It seems to happen pretty consistently when you try to include/exclude specific rows from the sync.
It's now logged under t...