Comments
Sort by recent activity
Thanks Eddie.
If possible (from our perspective at least) it would be preferable to retain the original encoding of each individual file (particularly as the encoding could vary between files in the same folder), but I guess that the ability to be able to specify the encoding would also be useful for the scenario where SQL Compare generates a new script for an object that exists in the database but does not exist in the folder.
Thanks
Chris / comments
Thanks Eddie.
If possible (from our perspective at least) it would be preferable to retain the original encoding of each individual file (particularly as the encoding could vary between files in th...
Hi Eddie
Thanks for your response.
I've previously tried amending the setting that you reference in your reply, but the setting only seems to affect the encoding of the single synchronisation script that SQL Compare generates when the requirement is to synchronise a database with another database or script folder.
I'm using SQL Compare the other way round, i.e. to update a set of existing scripts as a result of a comparison between a database and folder containing the scripts that I wish to update. The scripts are encoded as UTF-16, yet the encoding of the files is changed to Windows-1252 when SQL Compare has completed synchronisation, regardless of the setting of the 'Saving SQL Scripts -> Encoding' option. Ideally I'd like to retain the encoding of the original scripts.
Thanks
Chris / comments
Hi Eddie
Thanks for your response.
I've previously tried amending the setting that you reference in your reply, but the setting only seems to affect the encoding of the single synchronisation scrip...
This issue has now been resolved - there was a duplicate extended property in one of our scripts. [image]
It took some tracking down though - is verbose logging available in SQL Compare to help track these issues down?
Chris / comments
This issue has now been resolved - there was a duplicate extended property in one of our scripts.
It took some tracking down though - is verbose logging available in SQL Compare to help track thes...
You should be able to get this to work if you add NOLOCK into the 'Keywords to capitalize' list then use the following format:
SELECT *
FROM dbo.Table ( NOLOCK )
Note the space before NOLOCK.
Hope this helps.
Chris / comments
You should be able to get this to work if you add NOLOCK into the 'Keywords to capitalize' list then use the following format:
SELECT *
FROM dbo.Table ( NOLOCK )
Note the space before NOLOCK.
Hope ...