Comments
Sort by recent activity
I just upgraded and don't seem to be having this issue, However, I see that the refreshing of the databases showing that everything has change was not fixed for this release...darn! / comments
I just upgraded and don't seem to be having this issue, However, I see that the refreshing of the databases showing that everything has change was not fixed for this release...darn!
Well, the option to upgrade to the latest toolbelt doesn't exist for everyone. So, while the rest of the toolbelt that we have does support 2012/2014, we cannot get SQL Prompt to work, where as, SQL Source Control does. Just doesn't make any since.
Well, I just got an e-mail from Red-Gate, Toolbelt/SQL Prompt 5 is not supported on SSMS14 (and probably not 12). / comments
Well, the option to upgrade to the latest toolbelt doesn't exist for everyone. So, while the rest of the toolbelt that we have does support 2012/2014, we cannot get SQL Prompt to work, where as, S...
Ok, well, I have tried most of what you guys have said, and I had to make a change to my trigger, guess what, my error is back. It put Duplicate names back in the SQL file it generates, causing the issue again.
Is there a way to roll back to the previous version, where this DID NOT happen to me!
Thanks / comments
Ok, well, I have tried most of what you guys have said, and I had to make a change to my trigger, guess what, my error is back. It put Duplicate names back in the SQL file it generates, causing t...
FYI: Still happening in lastest update / comments
FYI: Still happening in lastest update
Just download and installed latest version 3.1.2.33, still same issue.
1. Open SSMS
2. Click on Linked Database
3. Wait for it complete compairson
4. Click on differetn Linked Database. Database in step 2 above now shows everything is out of data.... / comments
Just download and installed latest version 3.1.2.33, still same issue.
1. Open SSMS
2. Click on Linked Database
3. Wait for it complete compairson
4. Click on differetn Linked Database. Database i...
Any news on if and when this will be fixed. This did not happen for me, until the latest update of SSC 3.1.0.5208.
Thank / comments
Any news on if and when this will be fixed. This did not happen for me, until the latest update of SSC 3.1.0.5208.
Thank
We are having this issue on a Dedicated Model w/ SSC 3.1.0.5208. This does not happen in 3.0.13.4213.
I can get it to reproduce every time now.
1. Close SSMS
2. Open SSMS and connect to server
3. Click on a database that is linked and that has no changes pending. Wait for it to finish comparing. (Click on "Get Latest" tab and wait for "no new changes in source control")
4. Click on different database, can be linked or not, the database that was clicked in step 3 above, now shows that everything is out of data. (Blue circle on Green Server Icon and on every object in that database.) / comments
We are having this issue on a Dedicated Model w/ SSC 3.1.0.5208. This does not happen in 3.0.13.4213.
I can get it to reproduce every time now.
1. Close SSMS
2. Open SSMS and connect to server
3. C...
aspillert wrote:
Is it possible to exclude between sp_addextendedproperty differences between views in two databases? The Extended Property filter rule doesn't seem to do anything.
Also - can a COMPARE be done without considering the format or whitespace in the view code? I use SQL Prompt to format on our test and production systems, but the developers use "Design", so format is always different.
Thank you for any assistance
I have this same issue. I really don't want the REDGATE extended properties added via SQL Source Control to be in my migration scripts. SQL Compare, no matter what you have set in the OPTIONS for "IGNORE" Extended Properties, still adds it at the end of the script. This is really frustrating. / comments
aspillert wrote:
Is it possible to exclude between sp_addextendedproperty differences between views in two databases? The Extended Property filter rule doesn't seem to do anything.
Also - can ...
mmoore wrote:
aspillert wrote:
Is it possible to exclude between sp_addextendedproperty differences between views in two databases? The Extended Property filter rule doesn't seem to do anything.
Also - can a COMPARE be done without considering the format or whitespace in the view code? I use SQL Prompt to format on our test and production systems, but the developers use "Design", so format is always different.
Thank you for any assistance
I have this same issue. I really don't want the REDGATE extended properties added via SQL Source Control to be in my migration scripts. SQL Compare, no matter what you have set in the OPTIONS for "IGNORE" Extended Properties, still adds it at the end of the script. This is really frustrating.
After looking further into this, I noticed that this only applies to the Extended Properties that are added by SQL Source Control. They are always added, which in my case is pointless on my customer's Sql Server. / comments
mmoore wrote:
aspillert wrote:
Is it possible to exclude between sp_addextendedproperty differences between views in two databases? The Extended Property filter rule doesn't seem to do anyt...
andomar wrote:
I've just upgraded to SSMS 2012.
The installation left SSMS 2008 in place. After "checking for updates" from 2008, Red Gate Source Control appeared in the 2012 version.
Working fine so far!
Did you do the UPGRADE or did you do a CLEAN install? / comments
andomar wrote:
I've just upgraded to SSMS 2012.
The installation left SSMS 2008 in place. After "checking for updates" from 2008, Red Gate Source Control appeared in the 2012 version.
Working fi...