June 4, 2008 at 4:45 am
I am starting a project that requires me to merge the designs of two existing databases. They were developed for the same customer by 2 different organisations, on different SQL Servers, with different COLLATION properties. One of the customer's requirements is to add full-text searching to the combined database. Here is the detail:
The existing databases are [DATABASE1] and [DATABASE2]. Each has a single schema, [dbo]. I have created a development database, [DATABASE_NEW], which contains [Schema1] and [Schema2]. All the tables in [DATABASE1].[dbo] have been copied to [DATABASE_NEW].[Schema1]. All the tables in [DATABASE2].[dbo] have been copied to [DATABASE_NEW].[Schema2]. This is the starting point for my development work.
I now notice that all the varchar columns in [Schema1] are marked as "COLLATE SQL_Latin1_General_CP1_CI_AS". But all the varchar columns in [Schema2] are marked as "COLLATE Latin1_General_CI_AS".
Does anyone have experience of a similar scenario? In particular, has anyone added full-text indexing to a database like this? What are the problems that I might run into, further down the line?
I am tempted to try and standardise on one collation. Does anyone know of any easy way to do this?
All help and advice will be most gratefully received!
June 4, 2008 at 9:15 am
From what I can tell, those two collations are just different versions of the same thing (same collation, different name because of different versions of the server software). You shouldn't have any problems with it.
You might want to standardize it, just to be sure, but it probably doesn't matter.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply