rickgaribay.net

Space shuttles aren't built for rocket scientists, they're built for astronauts. The goal isn't the ship, its the moon.
posts - 303, comments - 180, trackbacks - 35

My Links

News

Where's Rick?


AgileAlliance deliver:Agile 2019- 4/29
Desert Code Camp, PHX - 10/11
VS Live Austin, TX - 6/3
VS Live SF - 6/17


About Me
Hands on leader, developer, architect specializing in the design and delivery of distributed systems in lean, agile environments with an emphasis in continuous improvement across people, process and technology. Speaker and published author with 18 years' experience leading the delivery of large and/or complex, high-impact distributed solutions in Retail, Intelligent Transportation, and Gaming & Hospitality.

I'm currently a Principal Engineer at Amazon, within the North America Consumer organization leading our global listings strategy that enable bulk and non-bulk listing experiences for our WW Selling Partners via apps, devices and APIs.

Full bio

Note: All postings on this site are my own and don’t necessarily represent the views of my employer.



Check out my publications on Amazon Kindle!





Archives

Post Categories

Published Works

Renaming SQL Server 2005

When using VPC, it is common to clone machines and rename servers, which can pose a problem for platforms such as BizTalk Server which are configured to connect to a given machine name at installation/configuration time.

The first step in managing a rename is to reconfigure BizTalk using the BizTalk Configuration Tool, but there is an additional step that is required from a SQL Server perspective.

If you perform the following query within the master table in the SQL Server that houses the BTS databases, you will get a record that includes the following:

select * from sys.servers

server_id       name
=============================
0                 CurrentServer

Where the server name has changed to something like "NewServer" it is necessary to not only rename the machine and assign it a new SID, but also to rename the SQL server name.

To do so, execute the following statement which drops the server name (don't worry your databases will still remain intact):

exec sp_dropserver 'CurrentServer' GO

Next, execute the following statement, providing the new server name:

sp_addserver 'NewServer', LOCAL GO

Now, run the same query as above and the result should include the new server name:

server_id       name
=============================
0                 NewServer

Once this is complete, you will more than likely need to unconfigure and reconfigure your BTS installation. There are some components where this is not required, but I haven't quite figured out which are which yet.

Print | posted on Wednesday, January 16, 2008 4:22 PM | Filed Under [ Hardware Misc. ]

Comments have been closed on this topic.

Powered by: