Comments
Sort by recent activity
Sorry for the delay.
When using the shared model in the latest version (3.1) we now record the changes in a table called 'RG_AllObjects' in tempdb. If this table is removed or couldn't be created for whatever reason, then it might cause strange behaviour with the blue indicators.
Could you check if you have this table and if it's populated with data? / comments
Sorry for the delay.
When using the shared model in the latest version (3.1) we now record the changes in a table called 'RG_AllObjects' in tempdb. If this table is removed or couldn't be created f...
Are you using the shared model? Could other users linked to the same database be committing the changes? / comments
Are you using the shared model? Could other users linked to the same database be committing the changes?
ok, I think this needs investigating. Leave it with me.
I take it you're on the latest version (3.1.0.4583) / comments
ok, I think this needs investigating. Leave it with me.
I take it you're on the latest version (3.1.0.4583)
This sounds like a bug.
Could you send me the DDL for the object that keeps popping up on the commit tab? It could be some syntax were not handling correctly. / comments
This sounds like a bug.
Could you send me the DDL for the object that keeps popping up on the commit tab? It could be some syntax were not handling correctly.
Sorry you're hitting this issue.
This is actually a known problem with our existence check if the default constraint is not on the default schema. Our internal reference for this bug is SC-5670. It has already been fixed by our development team and should be available in the next SQL Compare update. (Any build > 10.2.0
1565).
The only workarounds would be to either turn off the existence checks, or modify the script to fully qualify the constraint in the existence check. / comments
Sorry you're hitting this issue.
This is actually a known problem with our existence check if the default constraint is not on the default schema. Our internal reference for this bug is SC-5670. It...
I've reproduced this, and can confirm that it's a bug with the integration pack in SSMS 2012. It seems to work ok for other versions.
I've logged this as bug RGE-228 for our development team to address.
Sorry for the inconvenience. / comments
I've reproduced this, and can confirm that it's a bug with the integration pack in SSMS 2012. It seems to work ok for other versions.
I've logged this as bug RGE-228 for our development team to add...
This looks like a bug with the SSMS Integration pack. I'll see if I can reproduce it.
If you launch SQL Compare itself and set up the project, does it work as expected? / comments
This looks like a bug with the SSMS Integration pack. I'll see if I can reproduce it.
If you launch SQL Compare itself and set up the project, does it work as expected?
Sorry for the delay, I missed you last update.
I'm pretty sure your sequence of steps are exactly what I was doing, so maybe this would be good to see happening on your machine.
When would be a good time to schedule a remote session? / comments
Sorry for the delay, I missed you last update.
I'm pretty sure your sequence of steps are exactly what I was doing, so maybe this would be good to see happening on your machine.
When would be a goo...
I've had a chance to try this out with Vault, but I can't reproduce the behaviour either.
This is how I tested it, maybe you can spot what I'm doing wrong:
1) Created a database called 'Test'
2) Linked to Vault repository
3) Created table 'Table_a'
4) Checked in, this was revision 596
5) Deployed revision 596 to another database (Test_B)
6) Outside of SQL Source Control I added a file text.txt to the repository. This was revision 597
7) Set revision 597 as the source and compared to Test_B. This was reported as identical (is there you would expect a drop of Table_a to be scripted?)
8) Added a view 'View_a' - this was revision 598
9) If I deployed 598, it added the view to Test_B
10) Set revision 597 as the source. This time it wanted to drop the view, but that's only because it was created in a later revision, so it worked as I expected.
Is this different to the behaviour you're seeing.
Could you send any reproduction steps that I could try out? / comments
I've had a chance to try this out with Vault, but I can't reproduce the behaviour either.
This is how I tested it, maybe you can spot what I'm doing wrong:
1) Created a database called 'Test'
2) Li...
The SQL Data Compare download is from here: http://downloads.red-gate.com/checkforu ... .0.885.exe
If you're having trouble with a http link, you could try our ftp site. ftp://support.red-gate.com/patches/SQLDataCompare/ / comments
The SQL Data Compare download is from here:http://downloads.red-gate.com/checkforu ... .0.885.exe
If you're having trouble with a http link, you could try our ftp site.ftp://support.red-gate.com/pa...