September 17, 2014 at 9:03 am
Hi,
I have to change the collation of a 3TB database, because it differs from the server collation. The database is not compressed atm. Is it better to change the collation first (creating a new db with the right collation, create objects und return data) and compress after that, or better to compress the db before the collation change?
Greetz
Michael
Greetz
Query Shepherd
September 17, 2014 at 10:00 am
I'd implement compression first, as it will reduce the number of reads that you have to do when reading data from database A (on the old collation) to database B (on the new collation).
However, test this first!
September 17, 2014 at 10:13 am
I'd change the collation first, since I think that will affect the compression. I believe the overall compression overhead, including I/O, would outweigh any advantages gained in I/O.
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply