December 23, 2016 at 5:40 am
Hi folks, bit of an odd one.
I have an inherited server that is showing a different server collation to that of the system databases.
From the install logs I can see it was originally built as SQL_Latin1_General_CP1_CI_AS
Properties of the instance show "SQL_Latin1_General_CP1_CI_AS"
Properties of the System DBs/Querying Sys.databases shows "Latin1_General_CI_AS" for DB ids 1-4.
The process of changing the server collation (correctly) in order to fix it isn't a problem and i'll sort this out in due course.
However, just thought "i'd throw it out there" for ideas as to how someone may have got the instance into this state in the first place? I thought the server\system db collations were one and the same.
Cheers
Rod
December 23, 2016 at 5:44 am
Rod
If you don't specify a collation when you create the database, it will indeed inherit the server collation. I'd say the most likely explanation for your situation is that somebody's backed up or scripted out a database on a server with a different collation and then created it on yours.
John
December 23, 2016 at 6:17 am
Thanks John for the response. These are system databases that aren't matched to the server collation...so the only thing I can think of is that master, msdb and model were restored from another server (with Latin1_General_CI_AS) that had the same name (sys.servers is correct and with the update date/time of the server install itself).
December 24, 2016 at 6:21 am
I wonder if the server was upgraded in-place from a lowerer version. My understanding is that the databases retain their collation and the instance will be upgraded.
My train of thought is that the collation of the system databases seems to be SQL 2008 and the instance itself SQL 2014.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply