| Author |
 Topic  |
|
|
JoelSBradley
2 Posts |
 Posted - 07/22/2008 : 14:33:27
|
I've just started using V5 of DB Ghost. A project scripted using the prior version of DB Ghost seems to have scripted tables and static data using Unicode, and everything else in Windows encoding (1252). Does anyone have any advice on what to standardize on? It appears that SQL Server Management Studio uses 1252, and I'm guessing many other Windows apps do the same; however, the new DB Ghost defaults to Unicode!
TIA,
Joel
|
|
|
leachm
124 Posts |
Posted - 07/23/2008 : 02:07:18
|
It's a matter of choice really, all tools can handle Unicode (except for the rapidly diminishing VSS) so that's why we decided to make it the default.
The previous version of DB Ghost (4.5) tried to always create scripts as 1252 unless they contained characters that weren't in the codepage in which case it then used Unicode. This actually caused some confusion and is why we just give you the explicit choice in 5.0.
Interestingly Visual Studio uses UTF-8 by default so that's something else to throw into the mix.
Do you have any issues editing your Unicode scripts using your favourite tools?
regards,
Malcolm Leach
www.innovartis.co.uk
DB Ghost Build, Compare and Synchronize = Change Management for SQL Server |
 |
|
|
JoelSBradley
2 Posts |
Posted - 07/23/2008 : 09:46:29
|
Hi, Malcolm (Mr Chipstead here)
The only problem I'm aware of is doing compares when the files don't have the same encoding. In those situations I have to figure out what the encoding is on each file, and save a copy of one of them elsewhere in matching encoding so the compare will work. Needless to say, it's a hassle, but I guess it all goes back to the Tower of Babel!
We're using Visual Studio and Team Foundation Server.
Thanks,
Joel
|
|
|
|
leachm
124 Posts |
 Posted - 07/23/2008 : 10:35:14
|
Chipstead, ah yes, of course - good to hear from you again 
That's another good reason for us making the choice of encoding explicit now - you can just choose an encoding and always be assured what will be output. If you want to change the encoding of your current files you could build a database and then re-script it all with the v5 Scripter to make sure you have a decent compare baseline again.
Cheers,
Malc |
|
|
|
sean
12 Posts |
Posted - 11/06/2008 : 03:56:07
|
Morning guys,
We are using v5.0.836 of Change Manager, and the option to "Build DB and apply changes to Target", in order to generate a script to build a new DB, and create a Diff script to upgrade an existing DB.
The new DB Script file is generated with an ANSI encoding, while the Diff script has a Unicode encoding. Is there any way of setting the encoding, as there is with the Data / Schema scripter tool?
Thanks,
Sean |
|
|
|
Mark Baekdal
86 Posts |
Posted - 11/06/2008 : 04:14:26
|
not presently - we are considering making this an option like it is in the scripter. As a matter of interest - why is this a problem?
regards,
Mark Baekdal
http://www.dbghost.com
http://www.innovartis.co.uk
Build, Comparison and Synchronization from Source Control = Database change management for SQL Server
|
|
|
| |
Topic |
|
|
|
Encoding/code pages
