Comments
Sort by recent activity
I agree with your 'best practice', however I'm sure there are lots of other people like myself who get handed a code base they did not develop and which is not all consistant. Off all the issues I've been having with SQL Compare creating scripts to can actually run, this one has been the most painful for me in terms of debugging and rewriting the scripts. / comments
I agree with your 'best practice', however I'm sure there are lots of other people like myself who get handed a code base they did not develop and which is not all consistant. Off all the issues I'...
Agreed, it probably could be considered a bug, but it is all these small issues that I've encountered that has made me have to spend lots of time diagnosing the errors and rewriting the scripts I get from SQL Compare. / comments
Agreed, it probably could be considered a bug, but it is all these small issues that I've encountered that has made me have to spend lots of time diagnosing the errors and rewriting the scripts I g...
It appears it is not a bug, but rather a limitation of SQL Server 7. SQL Server 2000 allows this view creation, and SQL Server 7 does not. So this type of error only happens when sync'ing from 2000 to 7. I'm not sure how you address other incompatabilities, but perhaps raising a warning would help. / comments
It appears it is not a bug, but rather a limitation of SQL Server 7. SQL Server 2000 allows this view creation, and SQL Server 7 does not. So this type of error only happens when sync'ing from 2000...