Yes just another installation. Click Next Next.. boom! Great.
Oops somebody just realised that there was some information missing initially about the collation. Of Course SQL DBAs don’t make mistakes so it must be somebody else right?
Besides also giving a thought to having a formal “Pre and post installation checklist” if one doesn’t exists or perhaps update it if it does exists.Next blog post perhaps..
Now… back to the problem at hand. How do we deal with this.
Well basically you can’t in the traditional way of making a small change from GUI or a quick script. I know not great news but all is not lost really. The earlier you find out about an installation having wrong collation the better before it goes live or out of your hand.
The way the workaround works is that you rebuild system databases with new settings. Since you are going to technically re-install (rebuild system databases) your configuration will be lost. So backup everything you want to restore or make note of.Again “Pre and post installation checklist”would be invaluable which would include questions to insist on from the source of request.
- Backup all databases, both System and users.
- Backup and / note all config
- Detach databases as after System rebuild you will only see an installation with fresh system databases.
- Job and security etc. (Hopefully you haven’t gone so far building or using with this server but if you did then yes)
From the command line at path of Installation media the following piece of commands needs to changed in the right places to start of.
SQL_Latin1_General_CP1_CI_AS is used just as an example of course, it should be replaced with whatever the correct one is.
Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=. /SQLSYSADMINACCOUNTS=domain\user /SAPWD=Longsecurepassw04d! /SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS
Hope this helpsAdvertisements