a database restore technique question...

background sql2k on nt4.
one of the disk stripe went bad during the weekend and our network admin
rebuilt the box and reinstalled sql2k w/ sp2 but he didnt' check what was
installed origionally. his restore is like this:
1. origional sql excutables and database files are located at d:\mssql\, he
renamed it to d:\mssql_x\
2. he reinstalled sql2k and system databases to d:\mssql\, after that he was
able to start the sql service again.
3. he then renamed d:\mssql\ to d:\mssql_y\, and renamed d:\mssql_x\ back to
d:\mssql\
but the sql service wouldn't start. he said that tenique worked a couple of
times at other occasions.
my questions:
1. what might go wrong this time?
2. what's wrong with this technique, there is no backup or restore involved.
almost sounds too easy to be true.
thank you.
What he should have done was copy over the old database files to the new
folder. It appears that perhaps the old executables got corrupted.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Steve Lin" <lins@.nospam.portptld.com> wrote in message
news:%234$J1ViJEHA.1392@.TK2MSFTNGP09.phx.gbl...
background sql2k on nt4.
one of the disk stripe went bad during the weekend and our network admin
rebuilt the box and reinstalled sql2k w/ sp2 but he didnt' check what was
installed origionally. his restore is like this:
1. origional sql excutables and database files are located at d:\mssql\, he
renamed it to d:\mssql_x\
2. he reinstalled sql2k and system databases to d:\mssql\, after that he was
able to start the sql service again.
3. he then renamed d:\mssql\ to d:\mssql_y\, and renamed d:\mssql_x\ back to
d:\mssql\
but the sql service wouldn't start. he said that tenique worked a couple of
times at other occasions.
my questions:
1. what might go wrong this time?
2. what's wrong with this technique, there is no backup or restore involved.
almost sounds too easy to be true.
thank you.
|||"...copy over the old database files to the new..."
does that include system files such as master, msdb and so on?
if that's the case, wouldn't you need to 'attach' all the databases?
his tenique simple renamed the original directory to the new directory.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:#cXyfpiJEHA.2412@.TK2MSFTNGP12.phx.gbl...
> What he should have done was copy over the old database files to the new
> folder. It appears that perhaps the old executables got corrupted.
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com/sql
>
> "Steve Lin" <lins@.nospam.portptld.com> wrote in message
> news:%234$J1ViJEHA.1392@.TK2MSFTNGP09.phx.gbl...
> background sql2k on nt4.
> one of the disk stripe went bad during the weekend and our network admin
> rebuilt the box and reinstalled sql2k w/ sp2 but he didnt' check what was
> installed origionally. his restore is like this:
> 1. origional sql excutables and database files are located at d:\mssql\,
he
> renamed it to d:\mssql_x\
> 2. he reinstalled sql2k and system databases to d:\mssql\, after that he
was
> able to start the sql service again.
> 3. he then renamed d:\mssql\ to d:\mssql_y\, and renamed d:\mssql_x\ back
to
> d:\mssql\
> but the sql service wouldn't start. he said that tenique worked a couple
of
> times at other occasions.
> my questions:
> 1. what might go wrong this time?
> 2. what's wrong with this technique, there is no backup or restore
involved.
> almost sounds too easy to be true.
> thank you.
>
|||For everything to be in synch, then yes, you would have to move all
databases - assuming none were corrupted. Simply renaming the directory
would make it point to all of the old stuff - including the executables. If
the original SQL Server had been shut down properly, you wouldn't need to
attach anything.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Steve Lin" <lins@.nospam.portptld.com> wrote in message
news:OsUOquiJEHA.228@.TK2MSFTNGP10.phx.gbl...
"...copy over the old database files to the new..."
does that include system files such as master, msdb and so on?
if that's the case, wouldn't you need to 'attach' all the databases?
his tenique simple renamed the original directory to the new directory.
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:#cXyfpiJEHA.2412@.TK2MSFTNGP12.phx.gbl...
> What he should have done was copy over the old database files to the new
> folder. It appears that perhaps the old executables got corrupted.
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com/sql
>
> "Steve Lin" <lins@.nospam.portptld.com> wrote in message
> news:%234$J1ViJEHA.1392@.TK2MSFTNGP09.phx.gbl...
> background sql2k on nt4.
> one of the disk stripe went bad during the weekend and our network admin
> rebuilt the box and reinstalled sql2k w/ sp2 but he didnt' check what was
> installed origionally. his restore is like this:
> 1. origional sql excutables and database files are located at d:\mssql\,
he
> renamed it to d:\mssql_x\
> 2. he reinstalled sql2k and system databases to d:\mssql\, after that he
was
> able to start the sql service again.
> 3. he then renamed d:\mssql\ to d:\mssql_y\, and renamed d:\mssql_x\ back
to
> d:\mssql\
> but the sql service wouldn't start. he said that tenique worked a couple
of
> times at other occasions.
> my questions:
> 1. what might go wrong this time?
> 2. what's wrong with this technique, there is no backup or restore
involved.
> almost sounds too easy to be true.
> thank you.
>