- Log-in to the active node.
- Trigger a full backup for all System and User Databases.
- Script out all log-ins.
- If there are any user databases, you will have to export the tables using BCP utility.
- Copy SQL Server 2008 install media folder to some local directory. For Eg: D:\SQL2008SP2
- Open command prompt and execute below command. Caution: This step will replace your current system databases with new ones with required collation. So please make sure you will be able to restore all logins and the user databases back after this activity.
Note: Please replace the values for /INSTANCENAME, /SQLSYSADMINACCOUNTS, /SAPWD and /SQLCOLLATION
Here you go !. Your SQL server has got new collation settings now. Please let me know if incase you experienced any issues.
- Now restore all logins and userdatabases using the scripts generated in step 3 and the tables exported in Step 4.
- SQL Server 2008 Standard/Enterprise/Developer edition install Media with Service pack 2.
- One IP address as SQL Cluster virtual IP and host-name as SQL Cluster virtual host-name. Our clients will have to use this host-name or IP to connect with this fail-over instance.
- One shared disk to place all our System DB files + error-logs etc
- Minimum two identical clustered Windows 2008 Servers.
- … Will be adding more. Couldn’t remember all of them at one shot. Please add any missed out points below as comments. Thanks in advance.
- Log-in to any one node and move all the cluster resources to that node.
- Navigate to the media directory and execute the below command. This is to make sure we don’t move all the SQL server binary files into C drive.
setup.exe /ACTION=INSTALLFAILOVERCLUSTER /INSTALLSHAREDDIR=”J:\Program Files\Microsoft SQL Server” /INSTALLSHAREDWOWDIR=”J:\Program Files (x86)\Microsoft SQL Server”.
- Follow the instructions on the setup wizard.
To be continue…
The below script helps in detecting, recording and alerting when ever a change is made to sp_config or SQL server configuration settings. This will help in pin-pointing any unnecessary changes happening to Our Beloved SQL Server…