Restore won't open

I have 2 SQL 2K servers, ea running Server2k SP4 and SQL2K SP4. In EnterPrise
Manager, when I right-click on my 2 main databases, choose All
Tasks...Restore, I then get a perpetual hour-glass & have to terminate ER to
stop it. If I do this for any of the sample databases, the Restore dialogue
opens. I even verified there were no open connections to the 2 databases in
question, & it happens on both servers. I had to do a command line restore.
The backup, etc works fine, just the restore won't open. It did this on SQL
SP3 & I hoped installing SP4 would fix it, but no go. Any ideas? I even
terminated any non-critical services to no avail, i.e. Backup Exec services,
Trend Micro AV, etc.
Ted
Possibly a LOT of backuphistory to read. Check out the number of rows in the backup history tables
in msdb. Also, read about sp_delete_backuphistory (which takes a long time to run in order to delete
a lot of backup history).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ted Cole" <Ted Cole@.discussions.microsoft.com> wrote in message
news:99032F45-145B-4500-ABCB-9B922BB540E1@.microsoft.com...
>I have 2 SQL 2K servers, ea running Server2k SP4 and SQL2K SP4. In EnterPrise
> Manager, when I right-click on my 2 main databases, choose All
> Tasks...Restore, I then get a perpetual hour-glass & have to terminate ER to
> stop it. If I do this for any of the sample databases, the Restore dialogue
> opens. I even verified there were no open connections to the 2 databases in
> question, & it happens on both servers. I had to do a command line restore.
> The backup, etc works fine, just the restore won't open. It did this on SQL
> SP3 & I hoped installing SP4 would fix it, but no go. Any ideas? I even
> terminated any non-critical services to no avail, i.e. Backup Exec services,
> Trend Micro AV, etc.
> Ted
sql

Restore won't open

I have 2 SQL 2K servers, ea running Server2k SP4 and SQL2K SP4. In EnterPris
e
Manager, when I right-click on my 2 main databases, choose All
Tasks...Restore, I then get a perpetual hour-glass & have to terminate ER to
stop it. If I do this for any of the sample databases, the Restore dialogue
opens. I even verified there were no open connections to the 2 databases in
question, & it happens on both servers. I had to do a command line restore.
The backup, etc works fine, just the restore won't open. It did this on SQL
SP3 & I hoped installing SP4 would fix it, but no go. Any ideas? I even
terminated any non-critical services to no avail, i.e. Backup Exec services,
Trend Micro AV, etc.
TedPossibly a LOT of backuphistory to read. Check out the number of rows in the
backup history tables
in msdb. Also, read about sp_delete_backuphistory (which takes a long time t
o run in order to delete
a lot of backup history).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ted Cole" <Ted Cole@.discussions.microsoft.com> wrote in message
news:99032F45-145B-4500-ABCB-9B922BB540E1@.microsoft.com...
>I have 2 SQL 2K servers, ea running Server2k SP4 and SQL2K SP4. In EnterPri
se
> Manager, when I right-click on my 2 main databases, choose All
> Tasks...Restore, I then get a perpetual hour-glass & have to terminate ER
to
> stop it. If I do this for any of the sample databases, the Restore dialogu
e
> opens. I even verified there were no open connections to the 2 databases i
n
> question, & it happens on both servers. I had to do a command line restore
.
> The backup, etc works fine, just the restore won't open. It did this on SQ
L
> SP3 & I hoped installing SP4 would fix it, but no go. Any ideas? I even
> terminated any non-critical services to no avail, i.e. Backup Exec service
s,
> Trend Micro AV, etc.
> Ted

Restore won't open

I have 2 SQL 2K servers, ea running Server2k SP4 and SQL2K SP4. In EnterPrise
Manager, when I right-click on my 2 main databases, choose All
Tasks...Restore, I then get a perpetual hour-glass & have to terminate ER to
stop it. If I do this for any of the sample databases, the Restore dialogue
opens. I even verified there were no open connections to the 2 databases in
question, & it happens on both servers. I had to do a command line restore.
The backup, etc works fine, just the restore won't open. It did this on SQL
SP3 & I hoped installing SP4 would fix it, but no go. Any ideas? I even
terminated any non-critical services to no avail, i.e. Backup Exec services,
Trend Micro AV, etc.
TedPossibly a LOT of backuphistory to read. Check out the number of rows in the backup history tables
in msdb. Also, read about sp_delete_backuphistory (which takes a long time to run in order to delete
a lot of backup history).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ted Cole" <Ted Cole@.discussions.microsoft.com> wrote in message
news:99032F45-145B-4500-ABCB-9B922BB540E1@.microsoft.com...
>I have 2 SQL 2K servers, ea running Server2k SP4 and SQL2K SP4. In EnterPrise
> Manager, when I right-click on my 2 main databases, choose All
> Tasks...Restore, I then get a perpetual hour-glass & have to terminate ER to
> stop it. If I do this for any of the sample databases, the Restore dialogue
> opens. I even verified there were no open connections to the 2 databases in
> question, & it happens on both servers. I had to do a command line restore.
> The backup, etc works fine, just the restore won't open. It did this on SQL
> SP3 & I hoped installing SP4 would fix it, but no go. Any ideas? I even
> terminated any non-critical services to no avail, i.e. Backup Exec services,
> Trend Micro AV, etc.
> Ted

Restore system dbs from SP3 to SP3a?

Can system databases (master, model, msdb) backed up from SQL2k SP3 be restored to an instance of SP3a? Can they be restored from SP3a to SP3? TIA!Not going to happen buddy. try installing a fresh copy of sql server somewhere else upgrade to sp3, restore your system db's there, upgrade to sp3a then move the system db's to the live server. hope this helps.|||Thanks - that's what I thought. However, how can it be determined which SP (3 or 3a) a given instance is running? @.@.version returns 8.00.760 for both of them, & Properties in EM show SP3 for both. I remember there being a way to find the build number, but I don't know how to get it. TIA.|||Check with MS website at the SP3/SP3a download pages. They usually have a section that tells you how to determine which SP you're currently running under.|||Even better: http://www.sqlteam.com/item.asp?ItemID=8318

Restore sys databases

Am i able to restore system databases to sql2005 from sql2k SP4 backup
dumps?
Thanks
No.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"mecn" <mecn2002@.yahoo.com> wrote in message
news:ud1tSqdUGHA.4884@.TK2MSFTNGP10.phx.gbl...
> Am i able to restore system databases to sql2005 from sql2k SP4 backup
> dumps?
> Thanks
>
|||thanks, Geoff. you saved me a lot of time searching it
"mecn" <mecn2002@.yahoo.com> wrote in message
news:ud1tSqdUGHA.4884@.TK2MSFTNGP10.phx.gbl...
> Am i able to restore system databases to sql2005 from sql2k SP4 backup
> dumps?
> Thanks
>
sql

Restore SQL2K on different machine

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...
>|||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...
>|||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...
>|||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...
>

Restore SQL2K on different machine

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...
>
|||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...
>
|||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...
>
|||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...
>

Restore SQL2K on different machine

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

Restore of System databases... in earlier to SQL 2K versions....

Restoring of Master/MSDB databases used in SQL 2K is a new feature in SQL2K?
How did earlier versions of SQL Server 2K use to restore the system
databases?
http://support.microsoft.com/default.aspx?scid=kb;en-us;169039
As per the above link it seems to be there is no trace of restoring the
MASTER or MSDB databases as explained in SQL 2K documentation.
Thank you for your comment,
AllenRestore of the system databases has worked the same way across all versions of SQL Server (well,
msdb was introduced in 6.0).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"AllenHubatka" <AllenHubtka_67@.hotmail.com> wrote in message
news:uhvZCEFqFHA.3160@.TK2MSFTNGP14.phx.gbl...
>
> Restoring of Master/MSDB databases used in SQL 2K is a new feature in SQL2K?
> How did earlier versions of SQL Server 2K use to restore the system
> databases?
> http://support.microsoft.com/default.aspx?scid=kb;en-us;169039
> As per the above link it seems to be there is no trace of restoring the
> MASTER or MSDB databases as explained in SQL 2K documentation.
> Thank you for your comment,
> Allen
>
>
>

Restore Newbie

I am trying to install and run a prototype VB.net application for review
I have desktop edition of SQL2K installed and running.
I have a .bak file that I need to load for the applications data
How do I do restore?
I've seen posts where one runs the restore command, but I cannot find an executable called restore.exe?Allan,
It's a T-SQL command.
RESTORE DATABASE.
Or, you can do it from Enterprise Manager.
Either way, look at RESTORE DATABASE in Books Online.
James Hokes
"Allan" <anonymous@.discussions.microsoft.com> wrote in message
news:E467A676-703B-4636-BAE0-19B4BB6DD55B@.microsoft.com...
> I am trying to install and run a prototype VB.net application for review
> I have desktop edition of SQL2K installed and running.
> I have a .bak file that I need to load for the applications data
> How do I do restore?
> I've seen posts where one runs the restore command, but I cannot find an
executable called restore.exe?
>
>

restore master to another box

Is it possible to Restore Master db from a backup to a box/ instance with
another name? Will it cause any problems?
--
sql2k sp3
TIA, ChrisRIt's possible, but kind of a risky proposition, and it really depends on what
you're trying to accomplish, why you're moving the database, other databases
involved, server and database configuration, etc. Check BOL "Restoring the
master Database from a Current Backup" and "Copying Databases to Other
Servers" for details.
You also might want to look at sqlservercentral.com - a couple of links I
found are
http://www.sqlservercentral.com/columnists/bknight/restoremaster.asp and
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=24&messageid=8387
Personally, I install SQL Server on the destination server and detatch /
attatch the databases from old to new server. There used to be a Knowlege
Base article Q245133 that had code to generate scripts to recreate the
logins, but I couldn't find it. Let me know if you need it and I'll mail the
code to you - mstuart_spamtastesgood@.gates.com - drop the _spamtastesgood, of
course :-)
Mike
"ChrisR" wrote:
> Is it possible to Restore Master db from a backup to a box/ instance with
> another name? Will it cause any problems?
> --
> sql2k sp3
> TIA, ChrisR
>
>|||For the moment Im only trying to do some Disaster Recovery planning.
"Mike" <mstuart_spamtastesgood@.gates.com> wrote in message
news:1BDC103A-A9E2-48F1-B93F-2C28C2118EA9@.microsoft.com...
> It's possible, but kind of a risky proposition, and it really depends on
what
> you're trying to accomplish, why you're moving the database, other
databases
> involved, server and database configuration, etc. Check BOL "Restoring
the
> master Database from a Current Backup" and "Copying Databases to Other
> Servers" for details.
> You also might want to look at sqlservercentral.com - a couple of links I
> found are
> http://www.sqlservercentral.com/columnists/bknight/restoremaster.asp and
>
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=24&messageid=
8387
> Personally, I install SQL Server on the destination server and detatch /
> attatch the databases from old to new server. There used to be a Knowlege
> Base article Q245133 that had code to generate scripts to recreate the
> logins, but I couldn't find it. Let me know if you need it and I'll mail
the
> code to you - mstuart_spamtastesgood@.gates.com - drop the _spamtastesgood,
of
> course :-)
> Mike
> "ChrisR" wrote:
> > Is it possible to Restore Master db from a backup to a box/ instance
with
> > another name? Will it cause any problems?
> >
> > --
> > sql2k sp3
> >
> > TIA, ChrisR
> >
> >
> >|||First and foremost, backup all your databases and test your backups! There's
nothing worse (professionally, anyway) than thinking you've got good backups
and you don't when you need them. Ask me how I know...
Read BOL on recovering master and practice recovering. You should be able
to copy your environment onto a second server for testing purposes by:
1 - installing SQL Server and service packs on another server,
2 - stop SQL Server on the test server,
3 - copy the system data and log files to another location,
4 - stop SQL Server on your source server and copy all data and log files
from source to test environment,
5 - then restart SQL Server.
You'll also need backups of the other system databases (model and msdb).
Probably won't need to worry about pubs or Northwind unless you've got some
custom code in those databases you want to keep.
You'll also want to script out the logins and passwords - see the KB article
I referred to earlier. Depending on the number of changes to your login
accounts, you might even want to script a job to run and recreate the file
auto-magically.
Assuming you're not running earlier that SQL 7.0, you won't need to worry
about scripting out CREATE and ALTER database statements to add space to your
data and log files (I'm probably getting the terminology wrong - it's been a
very long time since SQL 4.2 and 6.5!!), but you'll want to know where you
created your database data, log and backup files so you don't have to go
searching everywhere when the pressure is on and the boss is looking over
your shoulder.
Finally, document on paper in clear, readable text with pictures (if
necessary) how to go about restoring your environment. You might even want
to have a coworker 'monkey test' it for you (can a monkey read your
directions and successfully do whatever you wrote down).
It sounds like extreme overkill, but at 2:00 in the AM and the payroll
server is down and you're the person they come to, you will definitely look
like a hero if you can pull it off, and you may lose your job if you can't.
Good luck!
Mike
"ChrisR" wrote:
> For the moment Im only trying to do some Disaster Recovery planning.
>
> "Mike" <mstuart_spamtastesgood@.gates.com> wrote in message
> news:1BDC103A-A9E2-48F1-B93F-2C28C2118EA9@.microsoft.com...
> > It's possible, but kind of a risky proposition, and it really depends on
> what
> > you're trying to accomplish, why you're moving the database, other
> databases
> > involved, server and database configuration, etc. Check BOL "Restoring
> the
> > master Database from a Current Backup" and "Copying Databases to Other
> > Servers" for details.
> >
> > You also might want to look at sqlservercentral.com - a couple of links I
> > found are
> > http://www.sqlservercentral.com/columnists/bknight/restoremaster.asp and
> >
> http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=24&messageid=
> 8387
> >
> > Personally, I install SQL Server on the destination server and detatch /
> > attatch the databases from old to new server. There used to be a Knowlege
> > Base article Q245133 that had code to generate scripts to recreate the
> > logins, but I couldn't find it. Let me know if you need it and I'll mail
> the
> > code to you - mstuart_spamtastesgood@.gates.com - drop the _spamtastesgood,
> of
> > course :-)
> >
> > Mike
> >
> > "ChrisR" wrote:
> >
> > > Is it possible to Restore Master db from a backup to a box/ instance
> with
> > > another name? Will it cause any problems?
> > >
> > > --
> > > sql2k sp3
> > >
> > > TIA, ChrisR
> > >
> > >
> > >
>
>|||Mike I appreciate your response. But do all of your instructions hold true
for a box with another name? Also, your are referring to copying system db
files. Will that get me around the downfalls of restoring master to a box
with another name?
"Mike" <mstuart_spamtastesgood@.gates.com> wrote in message
news:4D09B9F2-B7D8-4824-9809-2188E93999BC@.microsoft.com...
> First and foremost, backup all your databases and test your backups!
There's
> nothing worse (professionally, anyway) than thinking you've got good
backups
> and you don't when you need them. Ask me how I know...
> Read BOL on recovering master and practice recovering. You should be able
> to copy your environment onto a second server for testing purposes by:
> 1 - installing SQL Server and service packs on another server,
> 2 - stop SQL Server on the test server,
> 3 - copy the system data and log files to another location,
> 4 - stop SQL Server on your source server and copy all data and log files
> from source to test environment,
> 5 - then restart SQL Server.
> You'll also need backups of the other system databases (model and msdb).
> Probably won't need to worry about pubs or Northwind unless you've got
some
> custom code in those databases you want to keep.
> You'll also want to script out the logins and passwords - see the KB
article
> I referred to earlier. Depending on the number of changes to your login
> accounts, you might even want to script a job to run and recreate the file
> auto-magically.
> Assuming you're not running earlier that SQL 7.0, you won't need to worry
> about scripting out CREATE and ALTER database statements to add space to
your
> data and log files (I'm probably getting the terminology wrong - it's been
a
> very long time since SQL 4.2 and 6.5!!), but you'll want to know where you
> created your database data, log and backup files so you don't have to go
> searching everywhere when the pressure is on and the boss is looking over
> your shoulder.
> Finally, document on paper in clear, readable text with pictures (if
> necessary) how to go about restoring your environment. You might even
want
> to have a coworker 'monkey test' it for you (can a monkey read your
> directions and successfully do whatever you wrote down).
> It sounds like extreme overkill, but at 2:00 in the AM and the payroll
> server is down and you're the person they come to, you will definitely
look
> like a hero if you can pull it off, and you may lose your job if you
can't.
> Good luck!
> Mike
>
> "ChrisR" wrote:
> > For the moment Im only trying to do some Disaster Recovery planning.
> >
> >
> > "Mike" <mstuart_spamtastesgood@.gates.com> wrote in message
> > news:1BDC103A-A9E2-48F1-B93F-2C28C2118EA9@.microsoft.com...
> > > It's possible, but kind of a risky proposition, and it really depends
on
> > what
> > > you're trying to accomplish, why you're moving the database, other
> > databases
> > > involved, server and database configuration, etc. Check BOL
"Restoring
> > the
> > > master Database from a Current Backup" and "Copying Databases to Other
> > > Servers" for details.
> > >
> > > You also might want to look at sqlservercentral.com - a couple of
links I
> > > found are
> > > http://www.sqlservercentral.com/columnists/bknight/restoremaster.asp
and
> > >
> >
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=24&messageid=
> > 8387
> > >
> > > Personally, I install SQL Server on the destination server and detatch
/
> > > attatch the databases from old to new server. There used to be a
Knowlege
> > > Base article Q245133 that had code to generate scripts to recreate the
> > > logins, but I couldn't find it. Let me know if you need it and I'll
mail
> > the
> > > code to you - mstuart_spamtastesgood@.gates.com - drop the
_spamtastesgood,
> > of
> > > course :-)
> > >
> > > Mike
> > >
> > > "ChrisR" wrote:
> > >
> > > > Is it possible to Restore Master db from a backup to a box/ instance
> > with
> > > > another name? Will it cause any problems?
> > > >
> > > > --
> > > > sql2k sp3
> > > >
> > > > TIA, ChrisR
> > > >
> > > >
> > > >
> >
> >
> >|||Chris,
I guess I don't understand what you mean by the other box. If I understand
correctly, you have your server (we'll say production for sake of arguement)
that you want to develop a DR plan for. You need to set up an environment to
develop and test a plan against. So, you need to go through the steps I
outlined earlier - including the system .mdf and .ldf files.
One thing I did forget (yikes!) was that the master database .mdf and .ldf
files that you copy from the production server will still think that the name
of the SQL Server instance is the name of the production server. Run
'sp_dropserver' and 'sp_addserver' (see BOL 'Renaming a Server') to change
the instance name to the name of the development / test server.
This isn't exactly a restore of 'master' in the strictest sense of the word.
Your master database contains all of the information that allows the SQL
Server engine to see all of the databases installed on that instance of SQL
Server. You're just copying the master database, and all of the other
databases from the production instance to the development / test instance of
SQL Server.
If my directions are still unclear, email me @.
mstuart_spamtastesgood@.gates.com (drop the 'spamtastesgood') with you number
and I'll try to clarify things for you.
Mike

restore Master question

sql2k sp3
Im doing some disaster recovery testing. I first did a
Full backup of Master and a User db. Then I modified some
data in the User db. So then I uninstalled/ reinstalled
SQL to simulate a total box failure. I then restored the
full backup of Master. Now the thing thats weird is that
the user db came back online without restoring it. It even
has the data changes that occured after the full backups.
How can it be? I thought I would have had to restore the
User db as well in order to preserve the data?
TIA, ChrisAfter you uninstalled SQL Server, did you delete your mdf and ldf files?|||Chris,
When you were trying "to simulate a total box failure"
you forgot do delete actual databases files.
Next time, try to delete all files in MSSQL\Data folder.
HTH
Igor
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:6ba801c40170$18fd60c0$a101280a@.phx.gbl...
> sql2k sp3
> Im doing some disaster recovery testing. I first did a
> Full backup of Master and a User db. Then I modified some
> data in the User db. So then I uninstalled/ reinstalled
> SQL to simulate a total box failure. I then restored the
> full backup of Master. Now the thing thats weird is that
> the user db came back online without restoring it. It even
> has the data changes that occured after the full backups.
> How can it be? I thought I would have had to restore the
> User db as well in order to preserve the data?
> TIA, Chris|||Doh!!! Someone else just pointed that out to me also.

>--Original Message--
>After you uninstalled SQL Server, did you delete your mdf
and ldf files?
>.
>

restore Master question

sql2k sp3
Im doing some disaster recovery testing. I first did a
Full backup of Master and a User db. Then I modified some
data in the User db. So then I uninstalled/ reinstalled
SQL to simulate a total box failure. I then restored the
full backup of Master. Now the thing thats weird is that
the user db came back online without restoring it. It even
has the data changes that occured after the full backups.
How can it be? I thought I would have had to restore the
User db as well in order to preserve the data?
TIA, ChrisAfter you uninstalled SQL Server, did you delete your mdf and ldf files?|||Chris,
When you were trying "to simulate a total box failure"
you forgot do delete actual databases files.
Next time, try to delete all files in MSSQL\Data folder.
HTH
Igor
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:6ba801c40170$18fd60c0$a101280a@.phx.gbl...
> sql2k sp3
> Im doing some disaster recovery testing. I first did a
> Full backup of Master and a User db. Then I modified some
> data in the User db. So then I uninstalled/ reinstalled
> SQL to simulate a total box failure. I then restored the
> full backup of Master. Now the thing thats weird is that
> the user db came back online without restoring it. It even
> has the data changes that occured after the full backups.
> How can it be? I thought I would have had to restore the
> User db as well in order to preserve the data?
> TIA, Chris|||Doh!!! Someone else just pointed that out to me also.
>--Original Message--
>After you uninstalled SQL Server, did you delete your mdf
and ldf files?
>.
>