Link to home
Create AccountLog in
Avatar of jana
janaFlag for United States of America

asked on

Change collation of sql2017 when freshly installed.

We have installed a fresh new SQL 2017 server but has wrong collation; what's the proper steps to successfully change the collation to the desired one?
ASKER CERTIFIED SOLUTION
Avatar of David Johnson, CD
David Johnson, CD
Flag of Canada image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of jana

ASKER

Yes, since it’s a new install and has no production databases just the database installed by the SQL install, we don’t need to rebuild right?

The databases that gets installed with a fresh new SQL don’t need rebuild?

If change collation as recommended by David, we will not lose any configurations, logins and any other server objects like linked servers?
Yes, it will need a rebuild so yes, you'll lose all configurations from the SQL Server instance.
User databases have their own collation (usually from the SQL Server instance where they were created) but changing a database collation only affects the current database and not the SQL Server instance.
Avatar of jana

ASKER

Understood, can you provide some link to full rebuild of the system databases.
@victor the commands given do not require a rebuild

A few days ago, I came across an issue where we had to change the SQL server instance collation and we were just asking the clients to rebuild the system databases to do so in the previous cases. But this time the client could not afford to do that and asked for a plan B.
Avatar of jana

ASKER

Ok.  Note the new sql install has no working database, just the system database that it install with a new installation.
@David, I read that article but it's hard to me to believe that a SQL Server instance collation change doesn't need a rebuild. Of course rayluvs should give a try to confirm that. Unfortunately I don't have any available SQL Server instance to play with the -q parameter (btw, I checked in MSDN and couldn't find that parameter. It might be one of the hidden ones).
raylus, can you tell us if the SQL Server instance has been rebuilt or not?
I would like to confirm that the -q parameter doesn't rebuild the SQL Server instance, i.e., you don't loose any server object during the process.
Avatar of jana

ASKER

No (seems to work fine)
Thank you for the confirmation.