Currently migrating a SQL application from an old Win2k cluster to some new
hardware.
The new hardware will run as a Win2K3SP1 cluster.
The App people would like to keep the names the same for all servers and
virtual services so that clients are not affected.
Downtime is not an option.
Whats the easiest way to do this?
Consider a DNS alias.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Rory Niland" <RoryNiland@.discussions.microsoft.com> wrote in message
news:DDCB983B-3F22-4360-8E07-91B02887ABB3@.microsoft.com...
Currently migrating a SQL application from an old Win2k cluster to some new
hardware.
The new hardware will run as a Win2K3SP1 cluster.
The App people would like to keep the names the same for all servers and
virtual services so that clients are not affected.
Downtime is not an option.
Whats the easiest way to do this?
|||Agreed, because you can't rename a SQL machine.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OvlMaCNcFHA.580@.TK2MSFTNGP15.phx.gbl...
> Consider a DNS alias.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "Rory Niland" <RoryNiland@.discussions.microsoft.com> wrote in message
> news:DDCB983B-3F22-4360-8E07-91B02887ABB3@.microsoft.com...
> Currently migrating a SQL application from an old Win2k cluster to some
> new
> hardware.
> The new hardware will run as a Win2K3SP1 cluster.
> The App people would like to keep the names the same for all servers and
> virtual services so that clients are not affected.
> Downtime is not an option.
> Whats the easiest way to do this?
>
Showing posts with label win2k. Show all posts
Showing posts with label win2k. Show all posts
Monday, March 26, 2012
Migrating a database
We have a database running under SQL Server 7 on a Win NT server. We
have recently added Win2K servers, created a new domain and installed
SQL Server 7 on one of the servers. I would like to be able to log into
either domain from a workstation, use Enterprise Manager to access
either database and use the migration tools to copy the database from
the NT server to the 2K server.
We have created a trust relationship that allows me to log into either
domain, but when I try to use Enterprise Manager to create a
registration to the database on the other domain, or try to use the
migration tool to copy the database, I get an error saying that my user
account cannot log into the other system. ( I have the same user name
and password on both domains and domain admin privileges).
Can this be done directly? How?
Do I need "linked servers"? -- It doesn't like my account to create this
either.
Do I need a "remote server"?
Reading the documentation creates more questions than answers. I would
appreciate someone pointing me in the right direction. ThanksWhat is the exact error you are seeing and which domain are you logging
into, the new one or the other one.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||When I'm logged into the NT domain and trying to register SQL Server on the 2K
server, I get "login failed for user 'patenaude'".
When I'm logged into the 2K domain and trying to register SQL server on the NT
server, I get " loged failed for user 'null'. Not associated with a trusted
SQL Server connection."
I get similar messages trying to set up a linked server.
"Rand Boyd [MS]" wrote:
> What is the exact error you are seeing and which domain are you logging
> into, the new one or the other one.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.|||When you are logged into the Windows NT domain are you trying to register
the SQL Server using NT or SQL authentication. The error indicates SQL
authentication. If so does the 'patenaude' SQL login exist? Is the password
correct?
When you are logging into the Win 2K domain, the error indicates that you
cannot be validated on the domain controller. That is where the null is
coming from. Check the security log of the domain controller for this
domain for errors related to this account. Also if you are logged on to the
workstation using a local account you will see this error.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I changed the system on the 2K server to use NT authentication, so now I get
the same error message about my user account not being valid. (The user id is
good, the password is good.) My workstation is a member of the NT domain and
the trust relationship is set up to the point where I can log into either
domain. The user name is the same on both domains. I have tried registering
across the domain from both directions, using the default log-in with NT
authentication, using the specific login with my user name and using the
specific log-in with each of the domains added ( NTdomain\user & 2Kdomain\user)
I get the same results each time. I looked in the event logs on the servers and
there is no mention of the attempt in any of the logs.
"Rand Boyd [MS]" wrote:
> When you are logged into the Windows NT domain are you trying to register
> the SQL Server using NT or SQL authentication. The error indicates SQL
> authentication. If so does the 'patenaude' SQL login exist? Is the password
> correct?
> When you are logging into the Win 2K domain, the error indicates that you
> cannot be validated on the domain controller. That is where the null is
> coming from. Check the security log of the domain controller for this
> domain for errors related to this account. Also if you are logged on to the
> workstation using a local account you will see this error.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
have recently added Win2K servers, created a new domain and installed
SQL Server 7 on one of the servers. I would like to be able to log into
either domain from a workstation, use Enterprise Manager to access
either database and use the migration tools to copy the database from
the NT server to the 2K server.
We have created a trust relationship that allows me to log into either
domain, but when I try to use Enterprise Manager to create a
registration to the database on the other domain, or try to use the
migration tool to copy the database, I get an error saying that my user
account cannot log into the other system. ( I have the same user name
and password on both domains and domain admin privileges).
Can this be done directly? How?
Do I need "linked servers"? -- It doesn't like my account to create this
either.
Do I need a "remote server"?
Reading the documentation creates more questions than answers. I would
appreciate someone pointing me in the right direction. ThanksWhat is the exact error you are seeing and which domain are you logging
into, the new one or the other one.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||When I'm logged into the NT domain and trying to register SQL Server on the 2K
server, I get "login failed for user 'patenaude'".
When I'm logged into the 2K domain and trying to register SQL server on the NT
server, I get " loged failed for user 'null'. Not associated with a trusted
SQL Server connection."
I get similar messages trying to set up a linked server.
"Rand Boyd [MS]" wrote:
> What is the exact error you are seeing and which domain are you logging
> into, the new one or the other one.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.|||When you are logged into the Windows NT domain are you trying to register
the SQL Server using NT or SQL authentication. The error indicates SQL
authentication. If so does the 'patenaude' SQL login exist? Is the password
correct?
When you are logging into the Win 2K domain, the error indicates that you
cannot be validated on the domain controller. That is where the null is
coming from. Check the security log of the domain controller for this
domain for errors related to this account. Also if you are logged on to the
workstation using a local account you will see this error.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I changed the system on the 2K server to use NT authentication, so now I get
the same error message about my user account not being valid. (The user id is
good, the password is good.) My workstation is a member of the NT domain and
the trust relationship is set up to the point where I can log into either
domain. The user name is the same on both domains. I have tried registering
across the domain from both directions, using the default log-in with NT
authentication, using the specific login with my user name and using the
specific log-in with each of the domains added ( NTdomain\user & 2Kdomain\user)
I get the same results each time. I looked in the event logs on the servers and
there is no mention of the attempt in any of the logs.
"Rand Boyd [MS]" wrote:
> When you are logged into the Windows NT domain are you trying to register
> the SQL Server using NT or SQL authentication. The error indicates SQL
> authentication. If so does the 'patenaude' SQL login exist? Is the password
> correct?
> When you are logging into the Win 2K domain, the error indicates that you
> cannot be validated on the domain controller. That is where the null is
> coming from. Check the security log of the domain controller for this
> domain for errors related to this account. Also if you are logged on to the
> workstation using a local account you will see this error.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
migrating 7.0 to 2000
i have computer with windows 2000 an sql 7.0 (computerA)
goal is windows 2003 with sql 2005
I see my choices as is:
A) upgrade win2k to 2k3 then upgrade sql7 on w2k3 to sql2k5 on win2k3.
(i see many potential problems with that)
B) have computerB with clean install of win2k3 and install sql2k5 on it.
if this is the case, what is the best / easiest way to get the database from 7 to 2k5? Database copy wizard? dts? attaching the db?
Anything else I should lookout for ?
thnx,
vextThere might be better answers, but I'd set up the new server with the software that you intend to run on it (Windows 2003, SQL 2005). I'd backup the existing database, and restore that backup onto the new server.
-PatP|||what is the actual difference between using the Database copy wizard and Restoring a backup? and is the datafile still the same structure in 2005? will the restore upgrade if not?|||Theoretically, there shouldn't be a difference between Restoring a Backup and Copying a Database. That leads to all kinds of amusing observations, but I'll behave myself (at least for now). The primary difference is that restoring a backup is logically much more "solid" in that there are far fewer ways for it to go wrong...
The Copy Database Wizard is free to make many assumptions, many of which have a significant impact on performance and operational simplicity. These assumptions should not affect the copy of the quality, but I'm often unpleasantly surprised by them.
Restoring a backup is much less problematic for me. While some things (features, objects, etc) might change due to the difference in software releases (SQL 7 to SQL 2005 is a big jump), at least in my experience there will be far fewer surprises than you'd get via the Copy Database Wizard.
-PatP|||understood.
thnx for the input. I will do a restore when the time comes. thnxsql
goal is windows 2003 with sql 2005
I see my choices as is:
A) upgrade win2k to 2k3 then upgrade sql7 on w2k3 to sql2k5 on win2k3.
(i see many potential problems with that)
B) have computerB with clean install of win2k3 and install sql2k5 on it.
if this is the case, what is the best / easiest way to get the database from 7 to 2k5? Database copy wizard? dts? attaching the db?
Anything else I should lookout for ?
thnx,
vextThere might be better answers, but I'd set up the new server with the software that you intend to run on it (Windows 2003, SQL 2005). I'd backup the existing database, and restore that backup onto the new server.
-PatP|||what is the actual difference between using the Database copy wizard and Restoring a backup? and is the datafile still the same structure in 2005? will the restore upgrade if not?|||Theoretically, there shouldn't be a difference between Restoring a Backup and Copying a Database. That leads to all kinds of amusing observations, but I'll behave myself (at least for now). The primary difference is that restoring a backup is logically much more "solid" in that there are far fewer ways for it to go wrong...
The Copy Database Wizard is free to make many assumptions, many of which have a significant impact on performance and operational simplicity. These assumptions should not affect the copy of the quality, but I'm often unpleasantly surprised by them.
Restoring a backup is much less problematic for me. While some things (features, objects, etc) might change due to the difference in software releases (SQL 7 to SQL 2005 is a big jump), at least in my experience there will be far fewer surprises than you'd get via the Copy Database Wizard.
-PatP|||understood.
thnx for the input. I will do a restore when the time comes. thnxsql
Subscribe to:
Posts (Atom)