MS SQL Server - Transer of databases to new server

Author

Transer of databases to new server

CapnOdie

2005-08-08, 8:23 pm

Good day everyone,

We have purchased and installed a new server due to growth in our databases.
I have been assigned the duty of transferring our current db's to the new
server. The current server is running Server 2000 and, of course, the new
server will be running 2003. I have a couple of questions:

1. What considerations need to be addressed moving the db's from 2000 to 2003?
2. What is the best transfer method? Backup and restore from disk? Backup
and restore from tape? DTS? A method I am not aware of?
3. The current server has a password that needs to be used in connection
information on the front-ends (MSAccess, Visual Studio 2002 .net, 3rd party
software products. I realize that those changes need to be made, but is there
a simple process that might be employed?
4. Any problems with the new server name?

I am sure I will have other questions as I prepare for this work, but I wish
to pro-actively attack all issues that I might encounter. So any information
that your time will allow you to address quickly will be greatly appreciated
and shared with others in the future. I thank all of you that can help.

CapnOdie
--
CapnOdie

unc27932@yahoo.com

2005-08-08, 8:23 pm

Are SQL versions are the same? SQL 2000 to SQL 2000 with same service
pack versions??

1. What considerations need to be addressed moving the db's from 2000
to 2003?
I don't know of any - but that does mean there aren't any
considerations.

2. What is the best transfer method? Backup and restore from disk?
Backup and restore from tape? DTS? A method I am not aware of?

I prefer Backup from one location & restore to the new location.
There's also detach & attach.

3. The current server has a password that needs to be used in
connection information on the front-ends (MSAccess, Visual Studio 2002
..net, 3rd party software products. I realize that those changes need to
be made, but is there a simple process that might be employed?

Not sure about this one.

4. Any problems with the new server name?

Not that I'm aware - all your clients will need to point to your new
server though for the databases.

Alejandro Mesa

2005-08-08, 8:23 pm

HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/defaul...kb;en-us;314546

AMB

"CapnOdie" wrote:

> Good day everyone,
>
> We have purchased and installed a new server due to growth in our databases.
> I have been assigned the duty of transferring our current db's to the new
> server. The current server is running Server 2000 and, of course, the new
> server will be running 2003. I have a couple of questions:
>
> 1. What considerations need to be addressed moving the db's from 2000 to 2003?
> 2. What is the best transfer method? Backup and restore from disk? Backup
> and restore from tape? DTS? A method I am not aware of?
> 3. The current server has a password that needs to be used in connection
> information on the front-ends (MSAccess, Visual Studio 2002 .net, 3rd party
> software products. I realize that those changes need to be made, but is there
> a simple process that might be employed?
> 4. Any problems with the new server name?
>
> I am sure I will have other questions as I prepare for this work, but I wish
> to pro-actively attack all issues that I might encounter. So any information
> that your time will allow you to address quickly will be greatly appreciated
> and shared with others in the future. I thank all of you that can help.
>
> CapnOdie
> --
> CapnOdie

CapnOdie

2005-08-08, 8:23 pm

Thanks for your quick responses. I have to let you know I thought I had done
an effectived search on the group for some information, but couldn't find
anything. I finally ran into some. I do appreciate your time and any further
info will be appreciated.
--
CapnOdie

"CapnOdie" wrote:

> Good day everyone,
>
> We have purchased and installed a new server due to growth in our databases.
> I have been assigned the duty of transferring our current db's to the new
> server. The current server is running Server 2000 and, of course, the new
> server will be running 2003. I have a couple of questions:
>
> 1. What considerations need to be addressed moving the db's from 2000 to 2003?
> 2. What is the best transfer method? Backup and restore from disk? Backup
> and restore from tape? DTS? A method I am not aware of?
> 3. The current server has a password that needs to be used in connection
> information on the front-ends (MSAccess, Visual Studio 2002 .net, 3rd party
> software products. I realize that those changes need to be made, but is there
> a simple process that might be employed?
> 4. Any problems with the new server name?
>
> I am sure I will have other questions as I prepare for this work, but I wish
> to pro-actively attack all issues that I might encounter. So any information
> that your time will allow you to address quickly will be greatly appreciated
> and shared with others in the future. I thank all of you that can help.
>
> CapnOdie
> --
> CapnOdie

Ian Murphy

2005-08-08, 8:23 pm

"CapnOdie" wrote:
[color=darkred]
> Thanks for your quick responses. I have to let you know I thought I had done
> an effectived search on the group for some information, but couldn't find
> anything. I finally ran into some. I do appreciate your time and any further
> info will be appreciated.
> --
> CapnOdie
>
>
> "CapnOdie" wrote:
>

Hi,

I did this recently for one of our production systems. Moved it from a
Win2K server running SQL 2000 SP3 to Win2K3 server running the same.

I used the Copy Database Wizard with no issues. Make sure that the account
that the SQL Server service is running under on the current server has
permissions to create/write to a share on the new server otherwise it will
fail.

I renamed the new server to the old server's name (for ease of client
connectivity) and was a bit apprehensive about this but, with the help of
Google and the Microsof Knowledge Base found this pretty straightforward.

Best thing to do, if you can, is get SQL Server Personal / Development on
your own machine by way of a test environment and create a test database on
the live server (if you are allowed). Then transfer back and forth between
the two to test procedures etc.

Hope this helps!

Cheers,

Ian

CapnOdie

2005-08-09, 7:23 am

Thanks Ian,
I am in fact persuing that track. I will soon transfer my databases to the
awaiting new server with plans to run tests using the new server as a 'test'
platform. I will check connectivity with my front-ends. Upon completion I
will then clear the server of my databases and re-do the process as a 'live'
transfer. Thanks to all of you for the valuable information and directions
to the appropriate information sources.
Good day to all of you!
--
CapnOdie

"Ian Murphy" wrote:

>
>
> "CapnOdie" wrote:
>
>
> Hi,
>
> I did this recently for one of our production systems. Moved it from a
> Win2K server running SQL 2000 SP3 to Win2K3 server running the same.
>
> I used the Copy Database Wizard with no issues. Make sure that the account
> that the SQL Server service is running under on the current server has
> permissions to create/write to a share on the new server otherwise it will
> fail.
>
> I renamed the new server to the old server's name (for ease of client
> connectivity) and was a bit apprehensive about this but, with the help of
> Google and the Microsof Knowledge Base found this pretty straightforward.
>
> Best thing to do, if you can, is get SQL Server Personal / Development on
> your own machine by way of a test environment and create a test database on
> the live server (if you are allowed). Then transfer back and forth between
> the two to test procedures etc.
>
> Hope this helps!
>
> Cheers,
>
> Ian

Sponsored Links