Hello,
Would anyone know or recommend/advise the easiest approach in bringing down
and retiring an existing SQL2K running on W2K Server and brining it up with
all of the data, jobs, etc. onto a newer server machine? Wondering if there
was a way maybe do a full server restore from one of our server backup tapes
instead of having to reinstall/reconfigure everything from scratch.
Thanks in advance.Imaging is one approach if you have an imaging software like StorageCraft or
Acronis. But a main consideration here is hardware and configuration. The
source and destination may have different disk configurations. Another
considertation maybe to use Win2K3 instead of Win2K. If what you're
intending to restore is simply SQL Server, just a backup of all system and
user database would be enough and a very good restore process
On the old SQL Server instance,
1) stop all applications accessing your SQL Server
2) backup all your system and user databases
3) identify the latest hotfix you have. This is necessary for you to
restore on the new one
On the new SQL Server instance,
1) Install SQL Server together with the service packs and hotfixes up to the
one you have on the old instance
2) start SQL Server in single-user mode using the sqlservr.exe -c -m
3) restore the master database and restart the SQL Server service
4) restore the msdb database - be sure the SQLAgent service is not runnig
before you do so
5) restore model database if necessary
6) reconfigure your tempdb if necessary
7) restore all user databases and reconfigure if necessary - file locations
in particular
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hello,
> Would anyone know or recommend/advise the easiest approach in bringing
> down and retiring an existing SQL2K running on W2K Server and brining it
> up with all of the data, jobs, etc. onto a newer server machine?
> Wondering if there was a way maybe do a full server restore from one of
> our server backup tapes instead of having to reinstall/reconfigure
> everything from scratch.
> Thanks in advance.
>|||Actually I personally am leaning more towards putting it on a w2k3 OS
instead of w2k but am concerned if there would be anything in w2k3 that
wouldn't support w2k as in the system files, ad/domain, etc? Like would you
happen to know if there were anything that was left out in w2k3 that was in
w2k?
Thanks a bunch for your quick and helpful reply. Much appreciated :)
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
> Imaging is one approach if you have an imaging software like StorageCraft
> or Acronis. But a main consideration here is hardware and configuration.
> The source and destination may have different disk configurations. Another
> considertation maybe to use Win2K3 instead of Win2K. If what you're
> intending to restore is simply SQL Server, just a backup of all system and
> user database would be enough and a very good restore process
> On the old SQL Server instance,
> 1) stop all applications accessing your SQL Server
> 2) backup all your system and user databases
> 3) identify the latest hotfix you have. This is necessary for you to
> restore on the new one
> On the new SQL Server instance,
> 1) Install SQL Server together with the service packs and hotfixes up to
> the one you have on the old instance
> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
> 3) restore the master database and restart the SQL Server service
> 4) restore the msdb database - be sure the SQLAgent service is not runnig
> before you do so
> 5) restore model database if necessary
> 6) reconfigure your tempdb if necessary
> 7) restore all user databases and reconfigure if necessary - file
> locations in particular
>
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining it
>> up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>|||Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just remember
to ignore the warning when you install SQL Server 2000 on a Win2K3 telling
you that you do not have SP3. Install the latest service pack after
installing SQL Server 2000
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
> Actually I personally am leaning more towards putting it on a w2k3 OS
> instead of w2k but am concerned if there would be anything in w2k3 that
> wouldn't support w2k as in the system files, ad/domain, etc? Like would
> you happen to know if there were anything that was left out in w2k3 that
> was in w2k?
> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>
> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like StorageCraft
>> or Acronis. But a main consideration here is hardware and configuration.
>> The source and destination may have different disk configurations.
>> Another considertation maybe to use Win2K3 instead of Win2K. If what
>> you're intending to restore is simply SQL Server, just a backup of all
>> system and user database would be enough and a very good restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not runnig
>> before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining it
>> up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>|||I guess 2 main things that come to mind on that w2k server is that I've
installed a certificate from an ms ca service (in use for network ssl 'Force
protocol encryption' SQL Server Network Utility) in which I can just do
another certificate request/install and some .dll's that a VB app uses but I
would think that these shouldn't be an issue in that w2k3 would definitely
continue to support these. Will look into it further. Thanks so much for
your speedy informative reply. Will greatly help out in clearing things up
and expediting my research :)
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>> Actually I personally am leaning more towards putting it on a w2k3 OS
>> instead of w2k but am concerned if there would be anything in w2k3 that
>> wouldn't support w2k as in the system files, ad/domain, etc? Like would
>> you happen to know if there were anything that was left out in w2k3 that
>> was in w2k?
>> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>>
>> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
>> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like
>> StorageCraft or Acronis. But a main consideration here is hardware and
>> configuration. The source and destination may have different disk
>> configurations. Another considertation maybe to use Win2K3 instead of
>> Win2K. If what you're intending to restore is simply SQL Server, just a
>> backup of all system and user database would be enough and a very good
>> restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not
>> runnig before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining
>> it up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>>
>|||Sorry if I'm over analyzing this perhaps but I can't seem to visualize some
of the "X" factors like how to keep the same server name, domain and IP
address the same after rebuilding/restoring the master db onto the new
machine since this holds the domain logins/jobs. Are there any websites
that can layout it out step by step in retiring an old w2k-sql2k and restore
it onto a newer machine with w2k3-sql2k?
Thanks for your helpful replies bass_player.
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>> Actually I personally am leaning more towards putting it on a w2k3 OS
>> instead of w2k but am concerned if there would be anything in w2k3 that
>> wouldn't support w2k as in the system files, ad/domain, etc? Like would
>> you happen to know if there were anything that was left out in w2k3 that
>> was in w2k?
>> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>>
>> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
>> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like
>> StorageCraft or Acronis. But a main consideration here is hardware and
>> configuration. The source and destination may have different disk
>> configurations. Another considertation maybe to use Win2K3 instead of
>> Win2K. If what you're intending to restore is simply SQL Server, just a
>> backup of all system and user database would be enough and a very good
>> restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not
>> runnig before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining
>> it up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>>
>|||Just a quick question in that did you mean w2k3 SP2 instead of SP3? My
coworker the network admin had w2k3 SP1 currently installed on our new
server and was wondering if he should go ahead and install SP2 which then
I'll install the sql2k or should I install sql2k first and then let him
install w2k3 SP2 and the rest of the windows updates?
Thanks again bass_player.
"bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
news:u$QuvTm3HHA.5724@.TK2MSFTNGP05.phx.gbl...
> Moving SQL Server 2000 from Win2K to Win2K3 will be just fine. Just
> remember to ignore the warning when you install SQL Server 2000 on a
> Win2K3 telling you that you do not have SP3. Install the latest service
> pack after installing SQL Server 2000
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:u%238963c3HHA.4584@.TK2MSFTNGP03.phx.gbl...
>> Actually I personally am leaning more towards putting it on a w2k3 OS
>> instead of w2k but am concerned if there would be anything in w2k3 that
>> wouldn't support w2k as in the system files, ad/domain, etc? Like would
>> you happen to know if there were anything that was left out in w2k3 that
>> was in w2k?
>> Thanks a bunch for your quick and helpful reply. Much appreciated :)
>>
>> "bass_player [SBS-MVP]" <bass_player@.mvps.org> wrote in message
>> news:uVKtk%2372HHA.5316@.TK2MSFTNGP04.phx.gbl...
>> Imaging is one approach if you have an imaging software like
>> StorageCraft or Acronis. But a main consideration here is hardware and
>> configuration. The source and destination may have different disk
>> configurations. Another considertation maybe to use Win2K3 instead of
>> Win2K. If what you're intending to restore is simply SQL Server, just a
>> backup of all system and user database would be enough and a very good
>> restore process
>> On the old SQL Server instance,
>> 1) stop all applications accessing your SQL Server
>> 2) backup all your system and user databases
>> 3) identify the latest hotfix you have. This is necessary for you to
>> restore on the new one
>> On the new SQL Server instance,
>> 1) Install SQL Server together with the service packs and hotfixes up to
>> the one you have on the old instance
>> 2) start SQL Server in single-user mode using the sqlservr.exe -c -m
>> 3) restore the master database and restart the SQL Server service
>> 4) restore the msdb database - be sure the SQLAgent service is not
>> runnig before you do so
>> 5) restore model database if necessary
>> 6) reconfigure your tempdb if necessary
>> 7) restore all user databases and reconfigure if necessary - file
>> locations in particular
>>
>> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
>> news:OmuenB62HHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hello,
>> Would anyone know or recommend/advise the easiest approach in bringing
>> down and retiring an existing SQL2K running on W2K Server and brining
>> it up with all of the data, jobs, etc. onto a newer server machine?
>> Wondering if there was a way maybe do a full server restore from one of
>> our server backup tapes instead of having to reinstall/reconfigure
>> everything from scratch.
>> Thanks in advance.
>>
>>
>
sql
