SQL Server: Changing Instance Collation

- Detach all user databases.
- Put the below command
setup.exe /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=[either named instance without servername defaultinstance] /SQLSYSADMINACCOUNTS="Admin_User" /SAPWD=****** /SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS
Here few things you need to keep in mind
1. setup.exe should be the source where you copied all your installer file from dvd to local drive.
2. InstanceName will not include the server name only the instance name.
3. If SQLServer authentication is enabled put the sa password like /SAPWD=***** after /SQLSYSADMINACCOUNTS=*****.
4. You can see the log files in below locations
     a. C:\Users\Saifur Shaon\AppData\Local\Temp\SQLSetup.log
     b. C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120805_132518


Source:
http://msdn.microsoft.com/en-us/library/ms179254.aspx

Comments

Post a Comment

Popular posts from this blog

Restoring Master, Model and MSDB from Netbackup

Restoring System Databases got two parts: Taking the instance in single user mode and Restoring the Master Database If you need to rebuild the system databases on top of this you can use the below command: "C:\Program Files\Microsoft SQL Server\ 100 \Setup Bootstrap\ SQLServer2008R2 \setup.exe" /ACTION=REBUILDDATABASE /INSTANCENAME=SQL008 /SQLSYSADMINACCOUNTS=domain\ServiceUserName /SAPWD="yourpasswordOfSAuser" /SQLCOLLATION="Latin1_General_CI_AS" here 100 is for SQL Server 2008R2. It can vary case by case. How to take instance to single user mode: Two situation can happen: 1. Standalone Instance  2. Failover Cluster Instance 1. Standalone Instance: Go to SQL Config Manager SQL Service Properties -> Advanced Properties -> Startup Parameters put -m; in the Startup Parameters Apply and Okay - it will ask to restart the SQL Service to take effect. Stop and Start the service from Config Manager or you can stop and serv...
Read more

Oracle Job Operations

As a DBA, often I need to deal with Client's Jobs. Sometimes the jobs got hault, needs to break etc etc. Here are some useful commands for this sort of operations. ## Job Owner Schema can do this execute dbms_job.remove(444); execute dbms_job.broken(444, true); ## If Sys User needs to remove the job exec SYS.DBMS_IJOB.REMOVE(444); ## to find which jobs are running SELECT a.sid, c.serial#, a.job, a.failures, to_char(a.this_date, 'mm/dd/yyyy hh:mi pm') startdatetime, b.what FROM dba_jobs_running a, dba_jobs b, v$session c WHERE a.job = b.job AND a.sid = c.sid order by a.this_date ##let say we have only sid and serial and we need to kill the process from both OS and database. So first we need to find out the SPID. this query for any RAC database select P.SPID ,S.SID ,S.SERIAL#, S.SCHEMANAME, S.PROGRAM, S.INST_ID, S.OSUSER, S.STATUS from gv$process p, gv$session s where P.ADDR=S.PADDR and S.SID=888 and s.serial#=9293; ## kill the job al...
Read more