Comments
Sort by recent activity
Unfortunately it is an unavoidable requirement that you are on at least service pack 3. This is because the vdi component essential to our tool does not work in a SQL Server with less than service pack 3.
You should be able to upgrade for free to service pack 3 or later.
Let me know if you need any more information. / comments
Unfortunately it is an unavoidable requirement that you are on at least service pack 3. This is because the vdi component essential to our tool does not work in a SQL Server with less than service ...
Unfortunately there is no shortcut to jump straight to the next difference in SQL Compare.
However, I think it's a really good idea, so I have added it to the SQL Compare 'wish list'. If the feature is approved, it will be included in a future version.
Regards, / comments
Unfortunately there is no shortcut to jump straight to the next difference in SQL Compare.
However, I think it's a really good idea, so I have added it to the SQL Compare 'wish list'. If the featur...
Thanks for letting us know how you resolved this. [image] / comments
Thanks for letting us know how you resolved this.
I’m not completely sure why you might be getting this error. There is a known issue that SQL Compare can have a problem with the collations on SQL Server 7 databases. What version is the database that is having the problem?
Do you have any other SQL 2000 databases that you can test SQL Compare with? I have also been looking at the Microsoft site and they do not think that SQL Server Personal Edition is supported under XP, maybe this is a factor. / comments
I’m not completely sure why you might be getting this error. There is a known issue that SQL Compare can have a problem with the collations on SQL Server 7 databases. What version is the database...
Where was this error reported? Was it through the console?
Looking at the SQL Backup log file should give you more information.
The default location for this is:
C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Backup\Log\(INSTANCE NAME)
Feel free to send it to support if you want us to take a look at it. support@red-gate.com / comments
Where was this error reported? Was it through the console?
Looking at the SQL Backup log file should give you more information.
The default location for this is:
C:\Documents and Settings\All Users...
I've looked into this with a colleague and there does not appear to be any way to customise the subject line of the backup report emails.
I will make the suggestion to development to include this in a future release. If it is possible I will update this post. / comments
I've looked into this with a colleague and there does not appear to be any way to customise the subject line of the backup report emails.
I will make the suggestion to development to include this i...
What version of SQL compare are you using?
Older versions of SQL compare can have issues if the database has a SQL Server 7 compatability level. / comments
What version of SQL compare are you using?
Older versions of SQL compare can have issues if the database has a SQL Server 7 compatability level.
Hi,
Sorry you have been kept in the dark for so long.
The development team have confirmed this as a bug with SQL Compare. It is currently scheduled to be fixed for version 6 of the software. / comments
Hi,
Sorry you have been kept in the dark for so long.
The development team have confirmed this as a bug with SQL Compare. It is currently scheduled to be fixed for version 6 of the software.
Thanks for your post.
Is the script that's being generated in a different order still functionally correct, or does are the scripts invalid every so often? / comments
Thanks for your post.
Is the script that's being generated in a different order still functionally correct, or does are the scripts invalid every so often?
Thanks for your post.
I haven't personally looking into this in any detail, so I'll have a word with the dev team to find out why it's been designed like this.
My assumption at this stage is that is that we don't analyse what has changed in the package, only that the package has changed, and therefore script the COMPILE because that's the safest thing to do in most situations.
I'm interested to know how the recomplile is invalidating other objects in your database. Is that just during the recompile, or is it breaking them completely in some way? / comments
Thanks for your post.
I haven't personally looking into this in any detail, so I'll have a word with the dev team to find out why it's been designed like this.
My assumption at this stage is that i...