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.
Showing posts with label runs. Show all posts
Showing posts with label runs. Show all posts
Wednesday, March 21, 2012
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.
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.
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 out of a domain
Hi
We have a SQL Server 2000 (SP4) that is in the domain and runs under a domain account. We wanted to move it to an area with no access to the domain so I removed the machine from the domain, rebooted. SQL Server would not start because it was set to run under the domain account -- fair enough :) So I set the account to be system in the services control panel applet. SQL Server would still not run, it tried to run netlogon then that failed as it was not in a domain. I rejoined the domain and the SQL Server is happy again (and still running under local system).
Was the problem that is was set to load under a domain account when the machine was booted? Is there something else I must do to get it running out of the domain?Hi
We have a SQL Server 2000 (SP4) that is in the domain and runs under a domain account. We wanted to move it to an area with no access to the domain so I removed the machine from the domain, rebooted. SQL Server would not start because it was set to run under the domain account -- fair enough :) So I set the account to be system in the services control panel applet. SQL Server would still not run, it tried to run netlogon then that failed as it was not in a domain. I rejoined the domain and the SQL Server is happy again (and still running under local system).
Was the problem that is was set to load under a domain account when the machine was booted? Is there something else I must do to get it running out of the domain?
During installation, when you specify the server to run under a Domain account, M$ "secures" several folders in the <install path>\Microsoft SQL Server\ directory. The account used to secure these folders is the same account under which SQL is set to run.
To remove a server from the domain:
1. Use EM to change the service account under which SQL runs. Set it either to localsystem or a local account on the server (my preference).
2. Verify that SQL Agent is also set to run either under localsystem or a local account.
3. Then remove the member server from the domain.
Regards,
hmscott|||Hi
Thanks for the reply. I should have mentioend that the server was not orogianlly installed running under a domain account -- it was converted. I assume the advice is the same?|||Hi
Thanks for the reply. I should have mentioend that the server was not orogianlly installed running under a domain account -- it was converted. I assume the advice is the same?
I should think so. If the service account was changed through the EM GUI, I believe that M$ changes permissions on the appropriate folders automagically. If the service account was changed ONLY in using the Services GUI, then I can't be certain.
Regards,
hmscott
We have a SQL Server 2000 (SP4) that is in the domain and runs under a domain account. We wanted to move it to an area with no access to the domain so I removed the machine from the domain, rebooted. SQL Server would not start because it was set to run under the domain account -- fair enough :) So I set the account to be system in the services control panel applet. SQL Server would still not run, it tried to run netlogon then that failed as it was not in a domain. I rejoined the domain and the SQL Server is happy again (and still running under local system).
Was the problem that is was set to load under a domain account when the machine was booted? Is there something else I must do to get it running out of the domain?Hi
We have a SQL Server 2000 (SP4) that is in the domain and runs under a domain account. We wanted to move it to an area with no access to the domain so I removed the machine from the domain, rebooted. SQL Server would not start because it was set to run under the domain account -- fair enough :) So I set the account to be system in the services control panel applet. SQL Server would still not run, it tried to run netlogon then that failed as it was not in a domain. I rejoined the domain and the SQL Server is happy again (and still running under local system).
Was the problem that is was set to load under a domain account when the machine was booted? Is there something else I must do to get it running out of the domain?
During installation, when you specify the server to run under a Domain account, M$ "secures" several folders in the <install path>\Microsoft SQL Server\ directory. The account used to secure these folders is the same account under which SQL is set to run.
To remove a server from the domain:
1. Use EM to change the service account under which SQL runs. Set it either to localsystem or a local account on the server (my preference).
2. Verify that SQL Agent is also set to run either under localsystem or a local account.
3. Then remove the member server from the domain.
Regards,
hmscott|||Hi
Thanks for the reply. I should have mentioend that the server was not orogianlly installed running under a domain account -- it was converted. I assume the advice is the same?|||Hi
Thanks for the reply. I should have mentioend that the server was not orogianlly installed running under a domain account -- it was converted. I assume the advice is the same?
I should think so. If the service account was changed through the EM GUI, I believe that M$ changes permissions on the appropriate folders automagically. If the service account was changed ONLY in using the Services GUI, then I can't be certain.
Regards,
hmscott
Monday, March 12, 2012
Moving SQL 2005 to new machine
I'm looking for help moving SQL Server to a new machine. The current
SQL machine runs Windows Server 2003 ... we recently upgraded SQL on
this machine from SQL 2000 to SQL 2005 (dev). The new machine runs
Windows Server 2003 (x64) and has a fesh install of SQL 2005 (dev,
x64).
I haven't seen any How To docs specifically for SQL 2005 on this topic,
but the information for 2000 seemed relevant enough. Following advice
I've read, my plan was to back up master, model, and msdb; then retore
master and then model and msdb; and then do the same for my user dbs.
To this point, I have not been able to restore master. This is how
it's gone:
Fresh install
Run mssqlserver in single-user mode ... restore master ... goes to 100%
... then produces error
Log specifies it's looking for mssqlsystemresource.mdf in wrong path
Realize that 32-bit version of SQL is installed causing path difference
("\Program Files (x86)\")
Uninstall SQL and reinstall with SQL x64
Run mssqlserver in single-user mode ... restore master ... goes to 100%
... then produces error
Log specifies it's looking for mssqlsystemresource.mdf STILL in wrong
path (directory structure on new machine has "\MSSQL.1\MSSQL\" path
while old machine had just "\MSSQL\")
SQL Server no longer starts (log shows "Could not open file" for
aforementioned file)
I'd be very grateful for some input. (btw, I've also attempted a
detach/attach approach, but wasn't able to detach system dbs easily.)
Thanks in advance.Hi
This article was updated to also cover SQL 2005:
http://support.microsoft.com/defaul...b;en-us;Q314546
John
"matty2112@.hotmail.com" wrote:
> I'm looking for help moving SQL Server to a new machine. The current
> SQL machine runs Windows Server 2003 ... we recently upgraded SQL on
> this machine from SQL 2000 to SQL 2005 (dev). The new machine runs
> Windows Server 2003 (x64) and has a fesh install of SQL 2005 (dev,
> x64).
> I haven't seen any How To docs specifically for SQL 2005 on this topic,
> but the information for 2000 seemed relevant enough. Following advice
> I've read, my plan was to back up master, model, and msdb; then retore
> master and then model and msdb; and then do the same for my user dbs.
> To this point, I have not been able to restore master. This is how
> it's gone:
> Fresh install
> Run mssqlserver in single-user mode ... restore master ... goes to 100%
> ... then produces error
> Log specifies it's looking for mssqlsystemresource.mdf in wrong path
> Realize that 32-bit version of SQL is installed causing path difference
> ("\Program Files (x86)\")
> Uninstall SQL and reinstall with SQL x64
> Run mssqlserver in single-user mode ... restore master ... goes to 100%
> ... then produces error
> Log specifies it's looking for mssqlsystemresource.mdf STILL in wrong
> path (directory structure on new machine has "\MSSQL.1\MSSQL\" path
> while old machine had just "\MSSQL\")
> SQL Server no longer starts (log shows "Could not open file" for
> aforementioned file)
> I'd be very grateful for some input. (btw, I've also attempted a
> detach/attach approach, but wasn't able to detach system dbs easily.)
> Thanks in advance.
>|||Hi
I noticed in another post that there may be an issue with the resource DB if
you move the master database.
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:CE7199E1-9C6D-412F-B83A-9D9F9756493B@.microsoft.com...[vbcol=seagreen]
> Hi
> This article was updated to also cover SQL 2005:
> http://support.microsoft.com/defaul...b;en-us;Q314546
> John
> "matty2112@.hotmail.com" wrote:
>
SQL machine runs Windows Server 2003 ... we recently upgraded SQL on
this machine from SQL 2000 to SQL 2005 (dev). The new machine runs
Windows Server 2003 (x64) and has a fesh install of SQL 2005 (dev,
x64).
I haven't seen any How To docs specifically for SQL 2005 on this topic,
but the information for 2000 seemed relevant enough. Following advice
I've read, my plan was to back up master, model, and msdb; then retore
master and then model and msdb; and then do the same for my user dbs.
To this point, I have not been able to restore master. This is how
it's gone:
Fresh install
Run mssqlserver in single-user mode ... restore master ... goes to 100%
... then produces error
Log specifies it's looking for mssqlsystemresource.mdf in wrong path
Realize that 32-bit version of SQL is installed causing path difference
("\Program Files (x86)\")
Uninstall SQL and reinstall with SQL x64
Run mssqlserver in single-user mode ... restore master ... goes to 100%
... then produces error
Log specifies it's looking for mssqlsystemresource.mdf STILL in wrong
path (directory structure on new machine has "\MSSQL.1\MSSQL\" path
while old machine had just "\MSSQL\")
SQL Server no longer starts (log shows "Could not open file" for
aforementioned file)
I'd be very grateful for some input. (btw, I've also attempted a
detach/attach approach, but wasn't able to detach system dbs easily.)
Thanks in advance.Hi
This article was updated to also cover SQL 2005:
http://support.microsoft.com/defaul...b;en-us;Q314546
John
"matty2112@.hotmail.com" wrote:
> I'm looking for help moving SQL Server to a new machine. The current
> SQL machine runs Windows Server 2003 ... we recently upgraded SQL on
> this machine from SQL 2000 to SQL 2005 (dev). The new machine runs
> Windows Server 2003 (x64) and has a fesh install of SQL 2005 (dev,
> x64).
> I haven't seen any How To docs specifically for SQL 2005 on this topic,
> but the information for 2000 seemed relevant enough. Following advice
> I've read, my plan was to back up master, model, and msdb; then retore
> master and then model and msdb; and then do the same for my user dbs.
> To this point, I have not been able to restore master. This is how
> it's gone:
> Fresh install
> Run mssqlserver in single-user mode ... restore master ... goes to 100%
> ... then produces error
> Log specifies it's looking for mssqlsystemresource.mdf in wrong path
> Realize that 32-bit version of SQL is installed causing path difference
> ("\Program Files (x86)\")
> Uninstall SQL and reinstall with SQL x64
> Run mssqlserver in single-user mode ... restore master ... goes to 100%
> ... then produces error
> Log specifies it's looking for mssqlsystemresource.mdf STILL in wrong
> path (directory structure on new machine has "\MSSQL.1\MSSQL\" path
> while old machine had just "\MSSQL\")
> SQL Server no longer starts (log shows "Could not open file" for
> aforementioned file)
> I'd be very grateful for some input. (btw, I've also attempted a
> detach/attach approach, but wasn't able to detach system dbs easily.)
> Thanks in advance.
>|||Hi
I noticed in another post that there may be an issue with the resource DB if
you move the master database.
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:CE7199E1-9C6D-412F-B83A-9D9F9756493B@.microsoft.com...[vbcol=seagreen]
> Hi
> This article was updated to also cover SQL 2005:
> http://support.microsoft.com/defaul...b;en-us;Q314546
> John
> "matty2112@.hotmail.com" wrote:
>
Moving SQL 2005 to new machine
I'm looking for help moving SQL Server to a new machine. The current
SQL machine runs Windows Server 2003 ... we recently upgraded SQL on
this machine from SQL 2000 to SQL 2005 (dev). The new machine runs
Windows Server 2003 (x64) and has a fesh install of SQL 2005 (dev,
x64).
I haven't seen any How To docs specifically for SQL 2005 on this topic,
but the information for 2000 seemed relevant enough. Following advice
I've read, my plan was to back up master, model, and msdb; then retore
master and then model and msdb; and then do the same for my user dbs.
To this point, I have not been able to restore master. This is how
it's gone:
Fresh install
Run mssqlserver in single-user mode ... restore master ... goes to 100%
... then produces error
Log specifies it's looking for mssqlsystemresource.mdf in wrong path
Realize that 32-bit version of SQL is installed causing path difference
("\Program Files (x86)\")
Uninstall SQL and reinstall with SQL x64
Run mssqlserver in single-user mode ... restore master ... goes to 100%
... then produces error
Log specifies it's looking for mssqlsystemresource.mdf STILL in wrong
path (directory structure on new machine has "\MSSQL.1\MSSQL\" path
while old machine had just "\MSSQL\")
SQL Server no longer starts (log shows "Could not open file" for
aforementioned file)
I'd be very grateful for some input. (btw, I've also attempted a
detach/attach approach, but wasn't able to detach system dbs easily.)
Thanks in advance.
Hi
This article was updated to also cover SQL 2005:
http://support.microsoft.com/default...;en-us;Q314546
John
"matty2112@.hotmail.com" wrote:
> I'm looking for help moving SQL Server to a new machine. The current
> SQL machine runs Windows Server 2003 ... we recently upgraded SQL on
> this machine from SQL 2000 to SQL 2005 (dev). The new machine runs
> Windows Server 2003 (x64) and has a fesh install of SQL 2005 (dev,
> x64).
> I haven't seen any How To docs specifically for SQL 2005 on this topic,
> but the information for 2000 seemed relevant enough. Following advice
> I've read, my plan was to back up master, model, and msdb; then retore
> master and then model and msdb; and then do the same for my user dbs.
> To this point, I have not been able to restore master. This is how
> it's gone:
> Fresh install
> Run mssqlserver in single-user mode ... restore master ... goes to 100%
> ... then produces error
> Log specifies it's looking for mssqlsystemresource.mdf in wrong path
> Realize that 32-bit version of SQL is installed causing path difference
> ("\Program Files (x86)\")
> Uninstall SQL and reinstall with SQL x64
> Run mssqlserver in single-user mode ... restore master ... goes to 100%
> ... then produces error
> Log specifies it's looking for mssqlsystemresource.mdf STILL in wrong
> path (directory structure on new machine has "\MSSQL.1\MSSQL\" path
> while old machine had just "\MSSQL\")
> SQL Server no longer starts (log shows "Could not open file" for
> aforementioned file)
> I'd be very grateful for some input. (btw, I've also attempted a
> detach/attach approach, but wasn't able to detach system dbs easily.)
> Thanks in advance.
>
|||Hi
I noticed in another post that there may be an issue with the resource DB if
you move the master database.
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:CE7199E1-9C6D-412F-B83A-9D9F9756493B@.microsoft.com...[vbcol=seagreen]
> Hi
> This article was updated to also cover SQL 2005:
> http://support.microsoft.com/default...;en-us;Q314546
> John
> "matty2112@.hotmail.com" wrote:
SQL machine runs Windows Server 2003 ... we recently upgraded SQL on
this machine from SQL 2000 to SQL 2005 (dev). The new machine runs
Windows Server 2003 (x64) and has a fesh install of SQL 2005 (dev,
x64).
I haven't seen any How To docs specifically for SQL 2005 on this topic,
but the information for 2000 seemed relevant enough. Following advice
I've read, my plan was to back up master, model, and msdb; then retore
master and then model and msdb; and then do the same for my user dbs.
To this point, I have not been able to restore master. This is how
it's gone:
Fresh install
Run mssqlserver in single-user mode ... restore master ... goes to 100%
... then produces error
Log specifies it's looking for mssqlsystemresource.mdf in wrong path
Realize that 32-bit version of SQL is installed causing path difference
("\Program Files (x86)\")
Uninstall SQL and reinstall with SQL x64
Run mssqlserver in single-user mode ... restore master ... goes to 100%
... then produces error
Log specifies it's looking for mssqlsystemresource.mdf STILL in wrong
path (directory structure on new machine has "\MSSQL.1\MSSQL\" path
while old machine had just "\MSSQL\")
SQL Server no longer starts (log shows "Could not open file" for
aforementioned file)
I'd be very grateful for some input. (btw, I've also attempted a
detach/attach approach, but wasn't able to detach system dbs easily.)
Thanks in advance.
Hi
This article was updated to also cover SQL 2005:
http://support.microsoft.com/default...;en-us;Q314546
John
"matty2112@.hotmail.com" wrote:
> I'm looking for help moving SQL Server to a new machine. The current
> SQL machine runs Windows Server 2003 ... we recently upgraded SQL on
> this machine from SQL 2000 to SQL 2005 (dev). The new machine runs
> Windows Server 2003 (x64) and has a fesh install of SQL 2005 (dev,
> x64).
> I haven't seen any How To docs specifically for SQL 2005 on this topic,
> but the information for 2000 seemed relevant enough. Following advice
> I've read, my plan was to back up master, model, and msdb; then retore
> master and then model and msdb; and then do the same for my user dbs.
> To this point, I have not been able to restore master. This is how
> it's gone:
> Fresh install
> Run mssqlserver in single-user mode ... restore master ... goes to 100%
> ... then produces error
> Log specifies it's looking for mssqlsystemresource.mdf in wrong path
> Realize that 32-bit version of SQL is installed causing path difference
> ("\Program Files (x86)\")
> Uninstall SQL and reinstall with SQL x64
> Run mssqlserver in single-user mode ... restore master ... goes to 100%
> ... then produces error
> Log specifies it's looking for mssqlsystemresource.mdf STILL in wrong
> path (directory structure on new machine has "\MSSQL.1\MSSQL\" path
> while old machine had just "\MSSQL\")
> SQL Server no longer starts (log shows "Could not open file" for
> aforementioned file)
> I'd be very grateful for some input. (btw, I've also attempted a
> detach/attach approach, but wasn't able to detach system dbs easily.)
> Thanks in advance.
>
|||Hi
I noticed in another post that there may be an issue with the resource DB if
you move the master database.
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:CE7199E1-9C6D-412F-B83A-9D9F9756493B@.microsoft.com...[vbcol=seagreen]
> Hi
> This article was updated to also cover SQL 2005:
> http://support.microsoft.com/default...;en-us;Q314546
> John
> "matty2112@.hotmail.com" wrote:
Moving SQL 2005 to new machine
I'm looking for help moving SQL Server to a new machine. The current
SQL machine runs Windows Server 2003 ... we recently upgraded SQL on
this machine from SQL 2000 to SQL 2005 (dev). The new machine runs
Windows Server 2003 (x64) and has a fesh install of SQL 2005 (dev,
x64).
I haven't seen any How To docs specifically for SQL 2005 on this topic,
but the information for 2000 seemed relevant enough. Following advice
I've read, my plan was to back up master, model, and msdb; then retore
master and then model and msdb; and then do the same for my user dbs.
To this point, I have not been able to restore master. This is how
it's gone:
Fresh install
Run mssqlserver in single-user mode ... restore master ... goes to 100%
... then produces error
Log specifies it's looking for mssqlsystemresource.mdf in wrong path
Realize that 32-bit version of SQL is installed causing path difference
("\Program Files (x86)\")
Uninstall SQL and reinstall with SQL x64
Run mssqlserver in single-user mode ... restore master ... goes to 100%
... then produces error
Log specifies it's looking for mssqlsystemresource.mdf STILL in wrong
path (directory structure on new machine has "\MSSQL.1\MSSQL\" path
while old machine had just "\MSSQL\")
SQL Server no longer starts (log shows "Could not open file" for
aforementioned file)
I'd be very grateful for some input. (btw, I've also attempted a
detach/attach approach, but wasn't able to detach system dbs easily.)
Thanks in advance.Hi
This article was updated to also cover SQL 2005:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314546
John
"matty2112@.hotmail.com" wrote:
> I'm looking for help moving SQL Server to a new machine. The current
> SQL machine runs Windows Server 2003 ... we recently upgraded SQL on
> this machine from SQL 2000 to SQL 2005 (dev). The new machine runs
> Windows Server 2003 (x64) and has a fesh install of SQL 2005 (dev,
> x64).
> I haven't seen any How To docs specifically for SQL 2005 on this topic,
> but the information for 2000 seemed relevant enough. Following advice
> I've read, my plan was to back up master, model, and msdb; then retore
> master and then model and msdb; and then do the same for my user dbs.
> To this point, I have not been able to restore master. This is how
> it's gone:
> Fresh install
> Run mssqlserver in single-user mode ... restore master ... goes to 100%
> ... then produces error
> Log specifies it's looking for mssqlsystemresource.mdf in wrong path
> Realize that 32-bit version of SQL is installed causing path difference
> ("\Program Files (x86)\")
> Uninstall SQL and reinstall with SQL x64
> Run mssqlserver in single-user mode ... restore master ... goes to 100%
> ... then produces error
> Log specifies it's looking for mssqlsystemresource.mdf STILL in wrong
> path (directory structure on new machine has "\MSSQL.1\MSSQL\" path
> while old machine had just "\MSSQL\")
> SQL Server no longer starts (log shows "Could not open file" for
> aforementioned file)
> I'd be very grateful for some input. (btw, I've also attempted a
> detach/attach approach, but wasn't able to detach system dbs easily.)
> Thanks in advance.
>|||Hi
I noticed in another post that there may be an issue with the resource DB if
you move the master database.
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:CE7199E1-9C6D-412F-B83A-9D9F9756493B@.microsoft.com...
> Hi
> This article was updated to also cover SQL 2005:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314546
> John
> "matty2112@.hotmail.com" wrote:
>> I'm looking for help moving SQL Server to a new machine. The current
>> SQL machine runs Windows Server 2003 ... we recently upgraded SQL on
>> this machine from SQL 2000 to SQL 2005 (dev). The new machine runs
>> Windows Server 2003 (x64) and has a fesh install of SQL 2005 (dev,
>> x64).
>> I haven't seen any How To docs specifically for SQL 2005 on this topic,
>> but the information for 2000 seemed relevant enough. Following advice
>> I've read, my plan was to back up master, model, and msdb; then retore
>> master and then model and msdb; and then do the same for my user dbs.
>> To this point, I have not been able to restore master. This is how
>> it's gone:
>> Fresh install
>> Run mssqlserver in single-user mode ... restore master ... goes to 100%
>> ... then produces error
>> Log specifies it's looking for mssqlsystemresource.mdf in wrong path
>> Realize that 32-bit version of SQL is installed causing path difference
>> ("\Program Files (x86)\")
>> Uninstall SQL and reinstall with SQL x64
>> Run mssqlserver in single-user mode ... restore master ... goes to 100%
>> ... then produces error
>> Log specifies it's looking for mssqlsystemresource.mdf STILL in wrong
>> path (directory structure on new machine has "\MSSQL.1\MSSQL\" path
>> while old machine had just "\MSSQL\")
>> SQL Server no longer starts (log shows "Could not open file" for
>> aforementioned file)
>> I'd be very grateful for some input. (btw, I've also attempted a
>> detach/attach approach, but wasn't able to detach system dbs easily.)
>> Thanks in advance.
>>
SQL machine runs Windows Server 2003 ... we recently upgraded SQL on
this machine from SQL 2000 to SQL 2005 (dev). The new machine runs
Windows Server 2003 (x64) and has a fesh install of SQL 2005 (dev,
x64).
I haven't seen any How To docs specifically for SQL 2005 on this topic,
but the information for 2000 seemed relevant enough. Following advice
I've read, my plan was to back up master, model, and msdb; then retore
master and then model and msdb; and then do the same for my user dbs.
To this point, I have not been able to restore master. This is how
it's gone:
Fresh install
Run mssqlserver in single-user mode ... restore master ... goes to 100%
... then produces error
Log specifies it's looking for mssqlsystemresource.mdf in wrong path
Realize that 32-bit version of SQL is installed causing path difference
("\Program Files (x86)\")
Uninstall SQL and reinstall with SQL x64
Run mssqlserver in single-user mode ... restore master ... goes to 100%
... then produces error
Log specifies it's looking for mssqlsystemresource.mdf STILL in wrong
path (directory structure on new machine has "\MSSQL.1\MSSQL\" path
while old machine had just "\MSSQL\")
SQL Server no longer starts (log shows "Could not open file" for
aforementioned file)
I'd be very grateful for some input. (btw, I've also attempted a
detach/attach approach, but wasn't able to detach system dbs easily.)
Thanks in advance.Hi
This article was updated to also cover SQL 2005:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314546
John
"matty2112@.hotmail.com" wrote:
> I'm looking for help moving SQL Server to a new machine. The current
> SQL machine runs Windows Server 2003 ... we recently upgraded SQL on
> this machine from SQL 2000 to SQL 2005 (dev). The new machine runs
> Windows Server 2003 (x64) and has a fesh install of SQL 2005 (dev,
> x64).
> I haven't seen any How To docs specifically for SQL 2005 on this topic,
> but the information for 2000 seemed relevant enough. Following advice
> I've read, my plan was to back up master, model, and msdb; then retore
> master and then model and msdb; and then do the same for my user dbs.
> To this point, I have not been able to restore master. This is how
> it's gone:
> Fresh install
> Run mssqlserver in single-user mode ... restore master ... goes to 100%
> ... then produces error
> Log specifies it's looking for mssqlsystemresource.mdf in wrong path
> Realize that 32-bit version of SQL is installed causing path difference
> ("\Program Files (x86)\")
> Uninstall SQL and reinstall with SQL x64
> Run mssqlserver in single-user mode ... restore master ... goes to 100%
> ... then produces error
> Log specifies it's looking for mssqlsystemresource.mdf STILL in wrong
> path (directory structure on new machine has "\MSSQL.1\MSSQL\" path
> while old machine had just "\MSSQL\")
> SQL Server no longer starts (log shows "Could not open file" for
> aforementioned file)
> I'd be very grateful for some input. (btw, I've also attempted a
> detach/attach approach, but wasn't able to detach system dbs easily.)
> Thanks in advance.
>|||Hi
I noticed in another post that there may be an issue with the resource DB if
you move the master database.
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:CE7199E1-9C6D-412F-B83A-9D9F9756493B@.microsoft.com...
> Hi
> This article was updated to also cover SQL 2005:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314546
> John
> "matty2112@.hotmail.com" wrote:
>> I'm looking for help moving SQL Server to a new machine. The current
>> SQL machine runs Windows Server 2003 ... we recently upgraded SQL on
>> this machine from SQL 2000 to SQL 2005 (dev). The new machine runs
>> Windows Server 2003 (x64) and has a fesh install of SQL 2005 (dev,
>> x64).
>> I haven't seen any How To docs specifically for SQL 2005 on this topic,
>> but the information for 2000 seemed relevant enough. Following advice
>> I've read, my plan was to back up master, model, and msdb; then retore
>> master and then model and msdb; and then do the same for my user dbs.
>> To this point, I have not been able to restore master. This is how
>> it's gone:
>> Fresh install
>> Run mssqlserver in single-user mode ... restore master ... goes to 100%
>> ... then produces error
>> Log specifies it's looking for mssqlsystemresource.mdf in wrong path
>> Realize that 32-bit version of SQL is installed causing path difference
>> ("\Program Files (x86)\")
>> Uninstall SQL and reinstall with SQL x64
>> Run mssqlserver in single-user mode ... restore master ... goes to 100%
>> ... then produces error
>> Log specifies it's looking for mssqlsystemresource.mdf STILL in wrong
>> path (directory structure on new machine has "\MSSQL.1\MSSQL\" path
>> while old machine had just "\MSSQL\")
>> SQL Server no longer starts (log shows "Could not open file" for
>> aforementioned file)
>> I'd be very grateful for some input. (btw, I've also attempted a
>> detach/attach approach, but wasn't able to detach system dbs easily.)
>> Thanks in advance.
>>
Subscribe to:
Posts (Atom)