Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
rnbguy
Constraint Violating Yak Guru
293 Posts |
 Posted - 2007-01-23 : 22:15:03
|
| i would like to change all my dbs to have the same collation, i wasnt involved in the creation of these dbs and therefor cant judge if this will be a dangrous thing to do... but itll help to change when performing queries, arre there any dangers in doing this? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-01-23 : 23:19:54
|
| Yes. You could run into case sensitivity issues. For instance, if your database was set to case insensitive and now you are switching to case sensitive and developers didn't follow the case sensitivity of objects, then you'll get object not found errors. For example, Table1 does not equal table1 on a case sensitive database. If any of these databases are for third party products, then you will need to check with the vendor to determine if they support the collation you are switching to. Also, you should test it in a test environment prior to rolling this out to production.What collation are you switching to?Tara Kizer |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2007-01-24 : 08:34:39
|
| Also: watch out for any behavioural differences if you data includes Foreign Characters (such as Accents and so on)Kristen |
|
|
|
rnbguy
Constraint Violating Yak Guru
293 Posts |
Posted - 2007-01-24 : 18:36:30
|
| thanx heaps guys |
|
|
|
|
|
|
are there any dangers of changing a db collation