Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

MSSQLFUN

I, Rohit Garg, am working as Consultant in IT Company. I am having an around 5 years of experience in MSSQL server & other Microsoft technologies. I am working as DBA in Microsoft SQL Server from last 5 years in e-Commerce, Telecom, Finance domain. In this tenure, I got a chance of working as Database administrator, Developer and trainer on SQL server 2000 to SQL Server 2012. I am holding Master’s degree in Computer Science along with certification in SQL Server & .Net. I like to learn new things by hand-on experience on regular basis. This journey is so far is delightful & valuable with the addition of wonderful friends.

Rename or Change SQL Server Standalone Named Instance

Today, We will go through with the steps of renaming or changing SQL Server Standalone Named Instance.

Renaming or Changing SQL Server Standalone Named Instance is almost same as SQL Server Standalone Default Instance. You can change a SQL server named SQLServerinstance1 to some other name, such as SQLServerNewinstance1, but the instance portion of the name, instance1, will remain unchanged.

Refer : Rename or Change SQL Server Standalone Default Instance ()

Step 1 : Check Current Instance & host name

Current Host Name : admin-0783e4076

Current SQL Instance Name : admin-0783e4076SQL2K5_2

Select @@ServerName ServerName, Host_name() HostName

Step 2 : Rename Host name & reboot the server

Step 3 : Try to connect with SQL server ADMIN-0783E4076SQL2K5_2 & you will face below error because no instance of server name [ADMIN-0783E4076SQL2K5_2] exists as server name got changed

Cannot connect to ADMIN-0783E4076SQL2K5_2.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

Step 4 : Try to connect with “.SQL2K5_2” And Re Check Instance & host name and Drop old server name from server list of SQL

Exec sp_dropserver [ADMIN-0783E4076SQL2K5_2]

Step 5 : Add new server name as default server in server list of SQL

Exec sp_addserver [Win2K3_1SQL2K5_2],local

You can check default & other server ddetails from sys.servers.

SELECT * FROM SYS.SERVERS

Step 6 : Restart SQL Services

Step 7 : Try to connect with [Win2K3_1SQL2K5_2] And Re Check Instance & host name

You are done !

If you liked this post, do like on Facebook at http://www.facebook.com/mssqlfun

Reference : Rohit Garg (http://mssqlfun.com/)


Comments

Leave a comment on the original post [mssqlfun.com, opens in a new window]

Loading comments...