Moving SQL server to new hardware

I have a domain controller "ServerA". I am going to be replacing this
hardware with a new server - "ServerB". Currently "ServerA" runs SQL 2000
standard and has one instance "ServerA". I have a number of applications
etc, that use data on ServerA. When I bring Server B up, is there a way to
have the instance name to be ServerA and does this still change my
connection strings etc? I am just looking for a way to replace the server,
and not have to change all of my connection strings across the enterprise.
Both serverA and serverB are windows 2003 and both are SQL 2000.
Looking forward to your advice.
See if this helps:
How to move SQL Server from one computer to another
http://vyaskn.tripod.com/moving_sql_server.htm
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Fredrick A. Zilz" <fzilz@.NOSPAM.interhealthusa.com> wrote in message
news:eayAUbuuEHA.2632@.TK2MSFTNGP12.phx.gbl...
I have a domain controller "ServerA". I am going to be replacing this
hardware with a new server - "ServerB". Currently "ServerA" runs SQL 2000
standard and has one instance "ServerA". I have a number of applications
etc, that use data on ServerA. When I bring Server B up, is there a way to
have the instance name to be ServerA and does this still change my
connection strings etc? I am just looking for a way to replace the server,
and not have to change all of my connection strings across the enterprise.
Both serverA and serverB are windows 2003 and both are SQL 2000.
Looking forward to your advice.

Moving SQL server to new hardware

I have a domain controller "ServerA". I am going to be replacing this
hardware with a new server - "ServerB". Currently "ServerA" runs SQL 2000
standard and has one instance "ServerA". I have a number of applications
etc, that use data on ServerA. When I bring Server B up, is there a way to
have the instance name to be ServerA and does this still change my
connection strings etc? I am just looking for a way to replace the server,
and not have to change all of my connection strings across the enterprise.
Both serverA and serverB are windows 2003 and both are SQL 2000.
Looking forward to your advice.See if this helps:
How to move SQL Server from one computer to another
http://vyaskn.tripod.com/moving_sql_server.htm
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Fredrick A. Zilz" <fzilz@.NOSPAM.interhealthusa.com> wrote in message
news:eayAUbuuEHA.2632@.TK2MSFTNGP12.phx.gbl...
I have a domain controller "ServerA". I am going to be replacing this
hardware with a new server - "ServerB". Currently "ServerA" runs SQL 2000
standard and has one instance "ServerA". I have a number of applications
etc, that use data on ServerA. When I bring Server B up, is there a way to
have the instance name to be ServerA and does this still change my
connection strings etc? I am just looking for a way to replace the server,
and not have to change all of my connection strings across the enterprise.
Both serverA and serverB are windows 2003 and both are SQL 2000.
Looking forward to your advice.

Moving SQL server to new hardware

I have a domain controller "ServerA". I am going to be replacing this
hardware with a new server - "ServerB". Currently "ServerA" runs SQL 2000
standard and has one instance "ServerA". I have a number of applications
etc, that use data on ServerA. When I bring Server B up, is there a way to
have the instance name to be ServerA and does this still change my
connection strings etc? I am just looking for a way to replace the server,
and not have to change all of my connection strings across the enterprise.
Both serverA and serverB are windows 2003 and both are SQL 2000.
Looking forward to your advice.See if this helps:
How to move SQL Server from one computer to another
http://vyaskn.tripod.com/moving_sql_server.htm
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Fredrick A. Zilz" <fzilz@.NOSPAM.interhealthusa.com> wrote in message
news:eayAUbuuEHA.2632@.TK2MSFTNGP12.phx.gbl...
I have a domain controller "ServerA". I am going to be replacing this
hardware with a new server - "ServerB". Currently "ServerA" runs SQL 2000
standard and has one instance "ServerA". I have a number of applications
etc, that use data on ServerA. When I bring Server B up, is there a way to
have the instance name to be ServerA and does this still change my
connection strings etc? I am just looking for a way to replace the server,
and not have to change all of my connection strings across the enterprise.
Both serverA and serverB are windows 2003 and both are SQL 2000.
Looking forward to your advice.

Moving Reporting Services

I have reporing services in serverA, and i want to move all the reports to a new server serverB.

ServerA Sqlserver2000, operating system windows2000 adv server

ServerB Sqlserver2005, operang system windows2003 server.

Is it true that i have to detach the db from one server and attach it on another. If this is corect what are the other steps i need to do after moving. please advice

Thanks in advance

When you install RS on the new machine (SQL RS 2005) you will want to select the option to configure your environment after the instal. You will then go into the RS Configuration Manager and choose the database that you attached to the system.

if you are wanting to upgrade your reports from RS2000 to RS2005 you will need to open your reports up in Visual Studio 2005. This will prompt you to upgrade the rdl files in your project to RS 2005. you should then re-Deploy all of your reports to the new report server.

|||

i have already installed the server with default configuration... Your post also mentions about Visual Studio2005, does that mean reports in RS2005 can be deloyed only from VS2005..cant it be done from earler version of VS.

I have fllowed the steps i mentioned earlier, restore DB from 2000 to 2005, and when i went into report server configuration manager, it did an upgrade and all the steps where successfull except for it is not geting intialized...

i will get the exact message later when i attend the issue again..which might give more info about the problem i am facing