Re: Moving SQL Server 2000 from NT4.0 to Windows 2003

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Scott Yu (ScottYu_at_discussions.microsoft.com)
Date: 11/02/04 

Date: Tue, 2 Nov 2004 12:29:04 -0800

Hey Steve,

Thanks for your advice. Yeah, I already read Keith Kratochvil article on
moving SQL Servers, but the article assumes you are moving to a new machine
with the same SP and OS. This is not the case with me. It doesn't mention
about difference in service packs or the fact that Windows 2003 only allows
SQL Server 2000 SP3 or higher and Active Directory in 2003.

> I'd be more concerned about moving to downlevel (i.e. SP3 to SP2) than your plan.
-----------------------------------------------------------------------------
Can't do that. Windows 2003 will not allow SQL Server SP less than 3. I
have to install SP3 on 2003 so I have to go uplevel.

So, you think moving(by detaching or using a bak file) the system
tables(Master, MSDB, tempdb and Model) will be okay. I'm going to name the
new server the same name as the old as well in a test domain, which is cut
off from the production domain.
Is there any order in which I need to restore or reattach the system table in?

Thanks Steve for the info and the links. I'll read them all this week.
Scott Yu

"Steve Thompson" wrote:

> Scott Yu" <ScottYu@discussions.microsoft.com> wrote in message
> news:9829CD45-5809-42F5-AE3A-437541B2903C@microsoft.com...
> > Can anyone give me hints on moving the whole SQL Server 2000 with SP2 on
> > NT4.0 to Windows 2003 running SP3? My primary concerns are the difference
> > between SP, OS and system tables(SQL Server 2000).
>
> Attached is an excellent post from Keith Kratochvil on moving SQL Server
> 2000 between servers. You should be OK on the various revision levels you
> have there... I'd be more concerned about moving to downlevel (i.e. SP3 to
> SP2) than your plan.
>
> Steve
> ~~~~~~~~~~~~~~~~
> The better approach would be to use BACKUP and RESTORE or sp_detach_db and
> sp_attach_db to restore/attach your database(s) to the new server. You can
> find lots of information within Books Online. Here are some great
> resources:
>
> INF: Disaster Recovery Articles for Microsoft SQL Server
> http://www.support.microsoft.com/?id=307775
>
> INF: Moving SQL Server databases to a new location with Detach/Attach
> http://www.support.microsoft.com/?id=224071
>
> HOW TO: Move Databases Between Computers That Are Running SQL Server
> http://www.support.microsoft.com/?id=314546
>
> INF: Using the WITH MOVE Option with the RESTORE Statement
> http://support.microsoft.com/?id=221465
>
> PRB: User Logon and/or Permission Errors After Restoring Dump
> http://www.support.microsoft.com/?id=168001
>
> HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
> http://www.support.microsoft.com/?id=246133
>
> PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
> http://www.support.microsoft.com/?id=274188
>
> How to Resolve Permission Issues When a Database Is Moved Between SQL
> Servers
> http://www.support.microsoft.com/?id=240872
>
> SAMPLE: Mapsids.exe Helps Map SIDs Between User and Master Databases When
> Database Is Moved
> http://www.support.microsoft.com/?id=298897
>
>
>
> Utility to map users to the correct login
> http://www.dbmaint.com/SyncSqlLogins.asp
>
> ~~~~~~~~~~~~~~~~
>
>
>

Relevant Pages

  • Re: why>?
    ... On your desktop-- you'll be running SQL Server behind the scenes. ... it isn't risky to allow end users to create databases. ... it is no more risky than giving you the ability to create spreadsheets. ... I'm not saying that Oracle and IBM are going away. ...
    (microsoft.public.excel)
  • Re: Please answer my queries for fresh Installation
    ... Moving SQL Server Databases ... Using WITH MOVE in a Restore to a New Location with Detach/Attach ... Disaster Recovery Articles for SQL Server ...
    (microsoft.public.sqlserver.server)
  • Re: Please answer my queries for fresh Installation
    ... You can restore MSDB as well as master. ... > SQL Server, It will create Master, MSDB databases. ...
    (microsoft.public.sqlserver.server)
  • Re: Moving SQL Server 2000 from NT4.0 to Windows 2003
    ... Detach your existing user databases, ... user databases (or RESTORE) to the new server. ... > Hey Steve, ... Windows 2003 will not allow SQL Server SP less than 3. ...
    (microsoft.public.sqlserver.server)
  • Re: The best elegant solution to override 65k rows limit in a sheet
    ... MDB is friggin dead.. ... SQL Server has taken over the world. ... than read-only access to central company databases. ... I learned to write queries in Access after an hours' ...
    (microsoft.public.excel)