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.
>
Showing posts with label restore. Show all posts
Showing posts with label restore. Show all posts
Tuesday, March 27, 2012
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.
>
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.
>
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.
>
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.
>
Thursday, March 22, 2012
A connection could not be established...Cannot open user default
Tibor Karaszi wrote:
Thanks for the information. That seems to have fixed the lost db server
issue in the drop down. Still can't get the damn app server to
connect to the db server though. Will keep searching.
Everyone may ignore my last post.
quote:
> Seems like the database is "lost", as you terminated the restore, and the
> logins that your EM registration login is using has that database as the
> default database. I suggest you login using ISQL.EXE and change default
> database using sp_defaultdb.
>
Thanks for the information. That seems to have fixed the lost db server
issue in the drop down. Still can't get the damn app server to
connect to the db server though. Will keep searching.
quote:
> Thanks for the information. That seems to have fixed the lost db server
> issue in the drop down. Still can't get the damn app server to connect
> to the db server though. Will keep searching.
Everyone may ignore my last post.
A column nullability inconsistency was detected in the metadata E
Hello, I am trying to restore a backup of a database that was taken in SQL
Server 2000 onto SQL Server 2005. It appears the action completes, but I ge
t
a list of errors. I have ran a checktable on the tables in question on both
our origional 2000 database and 2005, as well as a checkdb on the database i
n
question on our SQL Server 2005 and get no errors. Any ideas?
Database 'MyDatabase' running the upgrade step from version 539 to version
551.
A column nullability inconsistency was detected in the metadata of
indexWarning: A column nullability inconsistency was detected in the metadat
a
of index "_WA_Sys_claim_scrubber_37BBEBC3" (index_id = 34) on object ID
935062467 in database "MyDatabase". The index may be corrupt. Run DBCC
CHECKTABLE to verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of
index "_WA_Sys_abn_notifier_37BBEBC3" (index_id = 35) on object ID 935062467
in database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of
index "_WA_Sys_cptguidelines_37BBEBC3" (index_id = 36) on object ID 93506246
7
in database "Mydatabase". The index may be corrupt. Run DBCC CHECKTABLE to
verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of
index "_WA_Sys_federal_37BBEBC3" (index_id = 37) on object ID 935062467 in
database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of
index "_WA_Sys_medicarea_37BBEBC3" (index_id = 38) on object ID 935062467 in
database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
verify consistency.Judging by the names of these, they appear to be auto-created statistics (an
d not indexes). I'd drop
those and then re-try the upgrade. See the DROP STATISTICS command.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Aaron" <Aaron@.discussions.microsoft.com> wrote in message
news:5DF5A523-75C0-45E1-BE54-6901814D0110@.microsoft.com...
> Hello, I am trying to restore a backup of a database that was taken in SQ
L
> Server 2000 onto SQL Server 2005. It appears the action completes, but I
get
> a list of errors. I have ran a checktable on the tables in question on bo
th
> our origional 2000 database and 2005, as well as a checkdb on the database
in
> question on our SQL Server 2005 and get no errors. Any ideas?
> Database 'MyDatabase' running the upgrade step from version 539 to version
> 551.
> A column nullability inconsistency was detected in the metadata of
> indexWarning: A column nullability inconsistency was detected in the metad
ata
> of index "_WA_Sys_claim_scrubber_37BBEBC3" (index_id = 34) on object ID
> 935062467 in database "MyDatabase". The index may be corrupt. Run DBCC
> CHECKTABLE to verify consistency.
> Warning: A column nullability inconsistency was detected in the metadata o
f
> index "_WA_Sys_abn_notifier_37BBEBC3" (index_id = 35) on object ID 9350624
67
> in database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
> verify consistency.
> Warning: A column nullability inconsistency was detected in the metadata o
f
> index "_WA_Sys_cptguidelines_37BBEBC3" (index_id = 36) on object ID 935062
467
> in database "Mydatabase". The index may be corrupt. Run DBCC CHECKTABLE to
> verify consistency.
> Warning: A column nullability inconsistency was detected in the metadata o
f
> index "_WA_Sys_federal_37BBEBC3" (index_id = 37) on object ID 935062467 in
> database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
> verify consistency.
> Warning: A column nullability inconsistency was detected in the metadata o
f
> index "_WA_Sys_medicarea_37BBEBC3" (index_id = 38) on object ID 935062467
in
> database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
> verify consistency.
>
Server 2000 onto SQL Server 2005. It appears the action completes, but I ge
t
a list of errors. I have ran a checktable on the tables in question on both
our origional 2000 database and 2005, as well as a checkdb on the database i
n
question on our SQL Server 2005 and get no errors. Any ideas?
Database 'MyDatabase' running the upgrade step from version 539 to version
551.
A column nullability inconsistency was detected in the metadata of
indexWarning: A column nullability inconsistency was detected in the metadat
a
of index "_WA_Sys_claim_scrubber_37BBEBC3" (index_id = 34) on object ID
935062467 in database "MyDatabase". The index may be corrupt. Run DBCC
CHECKTABLE to verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of
index "_WA_Sys_abn_notifier_37BBEBC3" (index_id = 35) on object ID 935062467
in database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of
index "_WA_Sys_cptguidelines_37BBEBC3" (index_id = 36) on object ID 93506246
7
in database "Mydatabase". The index may be corrupt. Run DBCC CHECKTABLE to
verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of
index "_WA_Sys_federal_37BBEBC3" (index_id = 37) on object ID 935062467 in
database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of
index "_WA_Sys_medicarea_37BBEBC3" (index_id = 38) on object ID 935062467 in
database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
verify consistency.Judging by the names of these, they appear to be auto-created statistics (an
d not indexes). I'd drop
those and then re-try the upgrade. See the DROP STATISTICS command.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Aaron" <Aaron@.discussions.microsoft.com> wrote in message
news:5DF5A523-75C0-45E1-BE54-6901814D0110@.microsoft.com...
> Hello, I am trying to restore a backup of a database that was taken in SQ
L
> Server 2000 onto SQL Server 2005. It appears the action completes, but I
get
> a list of errors. I have ran a checktable on the tables in question on bo
th
> our origional 2000 database and 2005, as well as a checkdb on the database
in
> question on our SQL Server 2005 and get no errors. Any ideas?
> Database 'MyDatabase' running the upgrade step from version 539 to version
> 551.
> A column nullability inconsistency was detected in the metadata of
> indexWarning: A column nullability inconsistency was detected in the metad
ata
> of index "_WA_Sys_claim_scrubber_37BBEBC3" (index_id = 34) on object ID
> 935062467 in database "MyDatabase". The index may be corrupt. Run DBCC
> CHECKTABLE to verify consistency.
> Warning: A column nullability inconsistency was detected in the metadata o
f
> index "_WA_Sys_abn_notifier_37BBEBC3" (index_id = 35) on object ID 9350624
67
> in database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
> verify consistency.
> Warning: A column nullability inconsistency was detected in the metadata o
f
> index "_WA_Sys_cptguidelines_37BBEBC3" (index_id = 36) on object ID 935062
467
> in database "Mydatabase". The index may be corrupt. Run DBCC CHECKTABLE to
> verify consistency.
> Warning: A column nullability inconsistency was detected in the metadata o
f
> index "_WA_Sys_federal_37BBEBC3" (index_id = 37) on object ID 935062467 in
> database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
> verify consistency.
> Warning: A column nullability inconsistency was detected in the metadata o
f
> index "_WA_Sys_medicarea_37BBEBC3" (index_id = 38) on object ID 935062467
in
> database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
> verify consistency.
>
A column nullability inconsistency was detected in the metadata E
Hello, I am trying to restore a backup of a database that was taken in SQL
Server 2000 onto SQL Server 2005. It appears the action completes, but I get
a list of errors. I have ran a checktable on the tables in question on both
our origional 2000 database and 2005, as well as a checkdb on the database in
question on our SQL Server 2005 and get no errors. Any ideas?
Database 'MyDatabase' running the upgrade step from version 539 to version
551.
A column nullability inconsistency was detected in the metadata of
indexWarning: A column nullability inconsistency was detected in the metadata
of index "_WA_Sys_claim_scrubber_37BBEBC3" (index_id = 34) on object ID
935062467 in database "MyDatabase". The index may be corrupt. Run DBCC
CHECKTABLE to verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of
index "_WA_Sys_abn_notifier_37BBEBC3" (index_id = 35) on object ID 935062467
in database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of
index "_WA_Sys_cptguidelines_37BBEBC3" (index_id = 36) on object ID 935062467
in database "Mydatabase". The index may be corrupt. Run DBCC CHECKTABLE to
verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of
index "_WA_Sys_federal_37BBEBC3" (index_id = 37) on object ID 935062467 in
database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of
index "_WA_Sys_medicarea_37BBEBC3" (index_id = 38) on object ID 935062467 in
database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
verify consistency.Judging by the names of these, they appear to be auto-created statistics (and not indexes). I'd drop
those and then re-try the upgrade. See the DROP STATISTICS command.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Aaron" <Aaron@.discussions.microsoft.com> wrote in message
news:5DF5A523-75C0-45E1-BE54-6901814D0110@.microsoft.com...
> Hello, I am trying to restore a backup of a database that was taken in SQL
> Server 2000 onto SQL Server 2005. It appears the action completes, but I get
> a list of errors. I have ran a checktable on the tables in question on both
> our origional 2000 database and 2005, as well as a checkdb on the database in
> question on our SQL Server 2005 and get no errors. Any ideas?
> Database 'MyDatabase' running the upgrade step from version 539 to version
> 551.
> A column nullability inconsistency was detected in the metadata of
> indexWarning: A column nullability inconsistency was detected in the metadata
> of index "_WA_Sys_claim_scrubber_37BBEBC3" (index_id = 34) on object ID
> 935062467 in database "MyDatabase". The index may be corrupt. Run DBCC
> CHECKTABLE to verify consistency.
> Warning: A column nullability inconsistency was detected in the metadata of
> index "_WA_Sys_abn_notifier_37BBEBC3" (index_id = 35) on object ID 935062467
> in database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
> verify consistency.
> Warning: A column nullability inconsistency was detected in the metadata of
> index "_WA_Sys_cptguidelines_37BBEBC3" (index_id = 36) on object ID 935062467
> in database "Mydatabase". The index may be corrupt. Run DBCC CHECKTABLE to
> verify consistency.
> Warning: A column nullability inconsistency was detected in the metadata of
> index "_WA_Sys_federal_37BBEBC3" (index_id = 37) on object ID 935062467 in
> database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
> verify consistency.
> Warning: A column nullability inconsistency was detected in the metadata of
> index "_WA_Sys_medicarea_37BBEBC3" (index_id = 38) on object ID 935062467 in
> database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
> verify consistency.
>sql
Server 2000 onto SQL Server 2005. It appears the action completes, but I get
a list of errors. I have ran a checktable on the tables in question on both
our origional 2000 database and 2005, as well as a checkdb on the database in
question on our SQL Server 2005 and get no errors. Any ideas?
Database 'MyDatabase' running the upgrade step from version 539 to version
551.
A column nullability inconsistency was detected in the metadata of
indexWarning: A column nullability inconsistency was detected in the metadata
of index "_WA_Sys_claim_scrubber_37BBEBC3" (index_id = 34) on object ID
935062467 in database "MyDatabase". The index may be corrupt. Run DBCC
CHECKTABLE to verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of
index "_WA_Sys_abn_notifier_37BBEBC3" (index_id = 35) on object ID 935062467
in database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of
index "_WA_Sys_cptguidelines_37BBEBC3" (index_id = 36) on object ID 935062467
in database "Mydatabase". The index may be corrupt. Run DBCC CHECKTABLE to
verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of
index "_WA_Sys_federal_37BBEBC3" (index_id = 37) on object ID 935062467 in
database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of
index "_WA_Sys_medicarea_37BBEBC3" (index_id = 38) on object ID 935062467 in
database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
verify consistency.Judging by the names of these, they appear to be auto-created statistics (and not indexes). I'd drop
those and then re-try the upgrade. See the DROP STATISTICS command.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Aaron" <Aaron@.discussions.microsoft.com> wrote in message
news:5DF5A523-75C0-45E1-BE54-6901814D0110@.microsoft.com...
> Hello, I am trying to restore a backup of a database that was taken in SQL
> Server 2000 onto SQL Server 2005. It appears the action completes, but I get
> a list of errors. I have ran a checktable on the tables in question on both
> our origional 2000 database and 2005, as well as a checkdb on the database in
> question on our SQL Server 2005 and get no errors. Any ideas?
> Database 'MyDatabase' running the upgrade step from version 539 to version
> 551.
> A column nullability inconsistency was detected in the metadata of
> indexWarning: A column nullability inconsistency was detected in the metadata
> of index "_WA_Sys_claim_scrubber_37BBEBC3" (index_id = 34) on object ID
> 935062467 in database "MyDatabase". The index may be corrupt. Run DBCC
> CHECKTABLE to verify consistency.
> Warning: A column nullability inconsistency was detected in the metadata of
> index "_WA_Sys_abn_notifier_37BBEBC3" (index_id = 35) on object ID 935062467
> in database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
> verify consistency.
> Warning: A column nullability inconsistency was detected in the metadata of
> index "_WA_Sys_cptguidelines_37BBEBC3" (index_id = 36) on object ID 935062467
> in database "Mydatabase". The index may be corrupt. Run DBCC CHECKTABLE to
> verify consistency.
> Warning: A column nullability inconsistency was detected in the metadata of
> index "_WA_Sys_federal_37BBEBC3" (index_id = 37) on object ID 935062467 in
> database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
> verify consistency.
> Warning: A column nullability inconsistency was detected in the metadata of
> index "_WA_Sys_medicarea_37BBEBC3" (index_id = 38) on object ID 935062467 in
> database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
> verify consistency.
>sql
Thursday, March 8, 2012
7.0 and 2000 .BAK incompatibility?
i just got a disk w/ a .bak file on it. when i tried to restore it on
my 2000 sql server instance it said the format was invalid. so, would i
get this error if the .bak version was created using version 7.0?
thanks,
arthur
Arthur,
7 --> 2000 shouldn't be a problem. Try using the HEADERONLY and
FILELISTONLY arguments of the RESTORE statement for the backup.
HTH
Jerry
"arthur" <alangham@.gmail.com> wrote in message
news:1129679111.225814.302070@.g14g2000cwa.googlegr oups.com...
>i just got a disk w/ a .bak file on it. when i tried to restore it on
> my 2000 sql server instance it said the format was invalid. so, would i
> get this error if the .bak version was created using version 7.0?
> thanks,
> arthur
>
|||the specific error i'm getting is RESTORE HEADERONLY is terminating
abnormally. i have no idea what the filelists are in the file. i'm
going to get w/ the peeps that made this file and see what's up. thanks.
|||Hi,
Then try using RESTORE FILELISTONLY OR use Enterprise manager -- All
tasks -- Restore
Filelistonly usage:-
Restore filelistonly from DISK='C:\Backup\backupfile.bak'
Thanks
Hari
SQL Server MVP
"arthur" <alangham@.gmail.com> wrote in message
news:1129680445.762037.102890@.g47g2000cwa.googlegr oups.com...
> the specific error i'm getting is RESTORE HEADERONLY is terminating
> abnormally. i have no idea what the filelists are in the file. i'm
> going to get w/ the peeps that made this file and see what's up. thanks.
>
|||Are you certain this is indeed a SQL Server backup file? It could just have been created with a beta
of SQL Server 7.0, but I think that SQL Server 2000 would give a more descriptive error message.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"arthur" <alangham@.gmail.com> wrote in message
news:1129680445.762037.102890@.g47g2000cwa.googlegr oups.com...
> the specific error i'm getting is RESTORE HEADERONLY is terminating
> abnormally. i have no idea what the filelists are in the file. i'm
> going to get w/ the peeps that made this file and see what's up. thanks.
>
my 2000 sql server instance it said the format was invalid. so, would i
get this error if the .bak version was created using version 7.0?
thanks,
arthur
Arthur,
7 --> 2000 shouldn't be a problem. Try using the HEADERONLY and
FILELISTONLY arguments of the RESTORE statement for the backup.
HTH
Jerry
"arthur" <alangham@.gmail.com> wrote in message
news:1129679111.225814.302070@.g14g2000cwa.googlegr oups.com...
>i just got a disk w/ a .bak file on it. when i tried to restore it on
> my 2000 sql server instance it said the format was invalid. so, would i
> get this error if the .bak version was created using version 7.0?
> thanks,
> arthur
>
|||the specific error i'm getting is RESTORE HEADERONLY is terminating
abnormally. i have no idea what the filelists are in the file. i'm
going to get w/ the peeps that made this file and see what's up. thanks.
|||Hi,
Then try using RESTORE FILELISTONLY OR use Enterprise manager -- All
tasks -- Restore
Filelistonly usage:-
Restore filelistonly from DISK='C:\Backup\backupfile.bak'
Thanks
Hari
SQL Server MVP
"arthur" <alangham@.gmail.com> wrote in message
news:1129680445.762037.102890@.g47g2000cwa.googlegr oups.com...
> the specific error i'm getting is RESTORE HEADERONLY is terminating
> abnormally. i have no idea what the filelists are in the file. i'm
> going to get w/ the peeps that made this file and see what's up. thanks.
>
|||Are you certain this is indeed a SQL Server backup file? It could just have been created with a beta
of SQL Server 7.0, but I think that SQL Server 2000 would give a more descriptive error message.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"arthur" <alangham@.gmail.com> wrote in message
news:1129680445.762037.102890@.g47g2000cwa.googlegr oups.com...
> the specific error i'm getting is RESTORE HEADERONLY is terminating
> abnormally. i have no idea what the filelists are in the file. i'm
> going to get w/ the peeps that made this file and see what's up. thanks.
>
7.0 and 2000 .BAK incompatibility?
i just got a disk w/ a .bak file on it. when i tried to restore it on
my 2000 sql server instance it said the format was invalid. so, would i
get this error if the .bak version was created using version 7.0?
thanks,
arthurArthur,
7 --> 2000 shouldn't be a problem. Try using the HEADERONLY and
FILELISTONLY arguments of the RESTORE statement for the backup.
HTH
Jerry
"arthur" <alangham@.gmail.com> wrote in message
news:1129679111.225814.302070@.g14g2000cwa.googlegroups.com...
>i just got a disk w/ a .bak file on it. when i tried to restore it on
> my 2000 sql server instance it said the format was invalid. so, would i
> get this error if the .bak version was created using version 7.0?
> thanks,
> arthur
>|||the specific error i'm getting is RESTORE HEADERONLY is terminating
abnormally. i have no idea what the filelists are in the file. i'm
going to get w/ the peeps that made this file and see what's up. thanks.|||Hi,
Then try using RESTORE FILELISTONLY OR use Enterprise manager -- All
tasks -- Restore
Filelistonly usage:-
Restore filelistonly from DISK='C:\Backup\backupfile.bak'
Thanks
Hari
SQL Server MVP
"arthur" <alangham@.gmail.com> wrote in message
news:1129680445.762037.102890@.g47g2000cwa.googlegroups.com...
> the specific error i'm getting is RESTORE HEADERONLY is terminating
> abnormally. i have no idea what the filelists are in the file. i'm
> going to get w/ the peeps that made this file and see what's up. thanks.
>|||Are you certain this is indeed a SQL Server backup file? It could just have
been created with a beta
of SQL Server 7.0, but I think that SQL Server 2000 would give a more descri
ptive error message.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"arthur" <alangham@.gmail.com> wrote in message
news:1129680445.762037.102890@.g47g2000cwa.googlegroups.com...
> the specific error i'm getting is RESTORE HEADERONLY is terminating
> abnormally. i have no idea what the filelists are in the file. i'm
> going to get w/ the peeps that made this file and see what's up. thanks.
>
my 2000 sql server instance it said the format was invalid. so, would i
get this error if the .bak version was created using version 7.0?
thanks,
arthurArthur,
7 --> 2000 shouldn't be a problem. Try using the HEADERONLY and
FILELISTONLY arguments of the RESTORE statement for the backup.
HTH
Jerry
"arthur" <alangham@.gmail.com> wrote in message
news:1129679111.225814.302070@.g14g2000cwa.googlegroups.com...
>i just got a disk w/ a .bak file on it. when i tried to restore it on
> my 2000 sql server instance it said the format was invalid. so, would i
> get this error if the .bak version was created using version 7.0?
> thanks,
> arthur
>|||the specific error i'm getting is RESTORE HEADERONLY is terminating
abnormally. i have no idea what the filelists are in the file. i'm
going to get w/ the peeps that made this file and see what's up. thanks.|||Hi,
Then try using RESTORE FILELISTONLY OR use Enterprise manager -- All
tasks -- Restore
Filelistonly usage:-
Restore filelistonly from DISK='C:\Backup\backupfile.bak'
Thanks
Hari
SQL Server MVP
"arthur" <alangham@.gmail.com> wrote in message
news:1129680445.762037.102890@.g47g2000cwa.googlegroups.com...
> the specific error i'm getting is RESTORE HEADERONLY is terminating
> abnormally. i have no idea what the filelists are in the file. i'm
> going to get w/ the peeps that made this file and see what's up. thanks.
>|||Are you certain this is indeed a SQL Server backup file? It could just have
been created with a beta
of SQL Server 7.0, but I think that SQL Server 2000 would give a more descri
ptive error message.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"arthur" <alangham@.gmail.com> wrote in message
news:1129680445.762037.102890@.g47g2000cwa.googlegroups.com...
> the specific error i'm getting is RESTORE HEADERONLY is terminating
> abnormally. i have no idea what the filelists are in the file. i'm
> going to get w/ the peeps that made this file and see what's up. thanks.
>
7.0 and 2000 .BAK incompatibility?
i just got a disk w/ a .bak file on it. when i tried to restore it on
my 2000 sql server instance it said the format was invalid. so, would i
get this error if the .bak version was created using version 7.0?
thanks,
arthurArthur,
7 --> 2000 shouldn't be a problem. Try using the HEADERONLY and
FILELISTONLY arguments of the RESTORE statement for the backup.
HTH
Jerry
"arthur" <alangham@.gmail.com> wrote in message
news:1129679111.225814.302070@.g14g2000cwa.googlegroups.com...
>i just got a disk w/ a .bak file on it. when i tried to restore it on
> my 2000 sql server instance it said the format was invalid. so, would i
> get this error if the .bak version was created using version 7.0?
> thanks,
> arthur
>|||the specific error i'm getting is RESTORE HEADERONLY is terminating
abnormally. i have no idea what the filelists are in the file. i'm
going to get w/ the peeps that made this file and see what's up. thanks.|||Hi,
Then try using RESTORE FILELISTONLY OR use Enterprise manager -- All
tasks -- Restore
Filelistonly usage:-
Restore filelistonly from DISK='C:\Backup\backupfile.bak'
Thanks
Hari
SQL Server MVP
"arthur" <alangham@.gmail.com> wrote in message
news:1129680445.762037.102890@.g47g2000cwa.googlegroups.com...
> the specific error i'm getting is RESTORE HEADERONLY is terminating
> abnormally. i have no idea what the filelists are in the file. i'm
> going to get w/ the peeps that made this file and see what's up. thanks.
>|||Are you certain this is indeed a SQL Server backup file? It could just have been created with a beta
of SQL Server 7.0, but I think that SQL Server 2000 would give a more descriptive error message.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"arthur" <alangham@.gmail.com> wrote in message
news:1129680445.762037.102890@.g47g2000cwa.googlegroups.com...
> the specific error i'm getting is RESTORE HEADERONLY is terminating
> abnormally. i have no idea what the filelists are in the file. i'm
> going to get w/ the peeps that made this file and see what's up. thanks.
>
my 2000 sql server instance it said the format was invalid. so, would i
get this error if the .bak version was created using version 7.0?
thanks,
arthurArthur,
7 --> 2000 shouldn't be a problem. Try using the HEADERONLY and
FILELISTONLY arguments of the RESTORE statement for the backup.
HTH
Jerry
"arthur" <alangham@.gmail.com> wrote in message
news:1129679111.225814.302070@.g14g2000cwa.googlegroups.com...
>i just got a disk w/ a .bak file on it. when i tried to restore it on
> my 2000 sql server instance it said the format was invalid. so, would i
> get this error if the .bak version was created using version 7.0?
> thanks,
> arthur
>|||the specific error i'm getting is RESTORE HEADERONLY is terminating
abnormally. i have no idea what the filelists are in the file. i'm
going to get w/ the peeps that made this file and see what's up. thanks.|||Hi,
Then try using RESTORE FILELISTONLY OR use Enterprise manager -- All
tasks -- Restore
Filelistonly usage:-
Restore filelistonly from DISK='C:\Backup\backupfile.bak'
Thanks
Hari
SQL Server MVP
"arthur" <alangham@.gmail.com> wrote in message
news:1129680445.762037.102890@.g47g2000cwa.googlegroups.com...
> the specific error i'm getting is RESTORE HEADERONLY is terminating
> abnormally. i have no idea what the filelists are in the file. i'm
> going to get w/ the peeps that made this file and see what's up. thanks.
>|||Are you certain this is indeed a SQL Server backup file? It could just have been created with a beta
of SQL Server 7.0, but I think that SQL Server 2000 would give a more descriptive error message.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"arthur" <alangham@.gmail.com> wrote in message
news:1129680445.762037.102890@.g47g2000cwa.googlegroups.com...
> the specific error i'm getting is RESTORE HEADERONLY is terminating
> abnormally. i have no idea what the filelists are in the file. i'm
> going to get w/ the peeps that made this file and see what's up. thanks.
>
Tuesday, March 6, 2012
64-bit restore with error
Hi all,
I am testing SQL Server 2000 64-bit on Itanium2 and have hit a problem.
Our current production system is running SQL Server 2000 32-bit SP3a. I
backed up the database (about 200+ GB) and restored it on SQL Server 2000
64-bit. After the restore was completed, I did a dbcc_checkdb and it came
back with various errors (see below for sample). I repeated the restore from
the same backup on another 32-bit box and dbcc checkdb came out clean. Any
idea what's causing the errors in dbcc checkdb on the 64-bit restore?
They're fixable using the repair option but it takes a long time and it
isn't really inspiring confidence in our management.
Btw, OS on both is Windows Server 2003 Enterprise SP1.
Any help will be much appreciated.
Thanks!
aK.
Small snippet of error messages:
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:76) with values (DetailActivityCurID = 55833475 and
WorkorderCurID = 316630 and SetTypeID = 4869 and ? = NULL) points to the
data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:77) with values (DetailActivityCurID = 55833476 and
WorkorderCurID = 316630 and SetTypeID = 4870 and ? = NULL) points to the
data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:78) with values (DetailActivityCurID = 55833477 and
WorkorderCurID = 316630 and SetTypeID = 4869 and ? = 1) points to the data
row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:79) with values (DetailActivityCurID = 55833478 and
WorkorderCurID = 316630 and SetTypeID = 4870 and ? = 1) points to the data
row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
(ID 1218103380) (index ID 4). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4447340:155) with values (ActivityDtime = Jul 14 2005 4:47PM
and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = NULL) points to the
data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
(ID 1218103380) (index ID 4). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4447340:160) with values (ActivityDtime = Jul 14 2005 4:47PM
and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = 1) points to the
data row identified by ().
Server: Msg 8945, Level 16, State 1, Line 1
Table error: Object ID 1218103380, index ID 5 will be rebuilt.
Hi
This looks like:
http://support.microsoft.com/default...b;en-us;884856
You may want to upgrade the 32 bit edition to SP4 and then migrate (to the
same version).
John
"Angie" <NoSpam_angie_kong@.hotmail.NoSpam.com> wrote in message
news:OPpLxmYwFHA.908@.tk2msftngp13.phx.gbl...
> Hi all,
> I am testing SQL Server 2000 64-bit on Itanium2 and have hit a problem.
> Our current production system is running SQL Server 2000 32-bit SP3a. I
> backed up the database (about 200+ GB) and restored it on SQL Server 2000
> 64-bit. After the restore was completed, I did a dbcc_checkdb and it came
> back with various errors (see below for sample). I repeated the restore
> from the same backup on another 32-bit box and dbcc checkdb came out
> clean. Any idea what's causing the errors in dbcc checkdb on the 64-bit
> restore? They're fixable using the repair option but it takes a long time
> and it isn't really inspiring confidence in our management.
> Btw, OS on both is Windows Server 2003 Enterprise SP1.
> Any help will be much appreciated.
> Thanks!
> aK.
>
> Small snippet of error messages:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:76) with values (DetailActivityCurID = 55833475 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:77) with values (DetailActivityCurID = 55833476 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:78) with values (DetailActivityCurID = 55833477 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:79) with values (DetailActivityCurID = 55833478 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:155) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = NULL) points to
> the data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:160) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = 1) points to the
> data row identified by ().
> Server: Msg 8945, Level 16, State 1, Line 1
> Table error: Object ID 1218103380, index ID 5 will be rebuilt.
>
|||This should process should work fine. What builds are the servers on? SP3a
or above and having the same build number on both servers will probably make
these go away.
"Angie" <NoSpam_angie_kong@.hotmail.NoSpam.com> wrote in message
news:OPpLxmYwFHA.908@.tk2msftngp13.phx.gbl...
> Hi all,
> I am testing SQL Server 2000 64-bit on Itanium2 and have hit a problem.
> Our current production system is running SQL Server 2000 32-bit SP3a. I
> backed up the database (about 200+ GB) and restored it on SQL Server 2000
> 64-bit. After the restore was completed, I did a dbcc_checkdb and it came
> back with various errors (see below for sample). I repeated the restore
> from the same backup on another 32-bit box and dbcc checkdb came out
> clean. Any idea what's causing the errors in dbcc checkdb on the 64-bit
> restore? They're fixable using the repair option but it takes a long time
> and it isn't really inspiring confidence in our management.
> Btw, OS on both is Windows Server 2003 Enterprise SP1.
> Any help will be much appreciated.
> Thanks!
> aK.
>
> Small snippet of error messages:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:76) with values (DetailActivityCurID = 55833475 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:77) with values (DetailActivityCurID = 55833476 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:78) with values (DetailActivityCurID = 55833477 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:79) with values (DetailActivityCurID = 55833478 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:155) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = NULL) points to
> the data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:160) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = 1) points to the
> data row identified by ().
> Server: Msg 8945, Level 16, State 1, Line 1
> Table error: Object ID 1218103380, index ID 5 will be rebuilt.
>
I am testing SQL Server 2000 64-bit on Itanium2 and have hit a problem.
Our current production system is running SQL Server 2000 32-bit SP3a. I
backed up the database (about 200+ GB) and restored it on SQL Server 2000
64-bit. After the restore was completed, I did a dbcc_checkdb and it came
back with various errors (see below for sample). I repeated the restore from
the same backup on another 32-bit box and dbcc checkdb came out clean. Any
idea what's causing the errors in dbcc checkdb on the 64-bit restore?
They're fixable using the repair option but it takes a long time and it
isn't really inspiring confidence in our management.
Btw, OS on both is Windows Server 2003 Enterprise SP1.
Any help will be much appreciated.
Thanks!
aK.
Small snippet of error messages:
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:76) with values (DetailActivityCurID = 55833475 and
WorkorderCurID = 316630 and SetTypeID = 4869 and ? = NULL) points to the
data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:77) with values (DetailActivityCurID = 55833476 and
WorkorderCurID = 316630 and SetTypeID = 4870 and ? = NULL) points to the
data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:78) with values (DetailActivityCurID = 55833477 and
WorkorderCurID = 316630 and SetTypeID = 4869 and ? = 1) points to the data
row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:79) with values (DetailActivityCurID = 55833478 and
WorkorderCurID = 316630 and SetTypeID = 4870 and ? = 1) points to the data
row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
(ID 1218103380) (index ID 4). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4447340:155) with values (ActivityDtime = Jul 14 2005 4:47PM
and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = NULL) points to the
data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
(ID 1218103380) (index ID 4). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4447340:160) with values (ActivityDtime = Jul 14 2005 4:47PM
and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = 1) points to the
data row identified by ().
Server: Msg 8945, Level 16, State 1, Line 1
Table error: Object ID 1218103380, index ID 5 will be rebuilt.
Hi
This looks like:
http://support.microsoft.com/default...b;en-us;884856
You may want to upgrade the 32 bit edition to SP4 and then migrate (to the
same version).
John
"Angie" <NoSpam_angie_kong@.hotmail.NoSpam.com> wrote in message
news:OPpLxmYwFHA.908@.tk2msftngp13.phx.gbl...
> Hi all,
> I am testing SQL Server 2000 64-bit on Itanium2 and have hit a problem.
> Our current production system is running SQL Server 2000 32-bit SP3a. I
> backed up the database (about 200+ GB) and restored it on SQL Server 2000
> 64-bit. After the restore was completed, I did a dbcc_checkdb and it came
> back with various errors (see below for sample). I repeated the restore
> from the same backup on another 32-bit box and dbcc checkdb came out
> clean. Any idea what's causing the errors in dbcc checkdb on the 64-bit
> restore? They're fixable using the repair option but it takes a long time
> and it isn't really inspiring confidence in our management.
> Btw, OS on both is Windows Server 2003 Enterprise SP1.
> Any help will be much appreciated.
> Thanks!
> aK.
>
> Small snippet of error messages:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:76) with values (DetailActivityCurID = 55833475 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:77) with values (DetailActivityCurID = 55833476 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:78) with values (DetailActivityCurID = 55833477 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:79) with values (DetailActivityCurID = 55833478 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:155) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = NULL) points to
> the data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:160) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = 1) points to the
> data row identified by ().
> Server: Msg 8945, Level 16, State 1, Line 1
> Table error: Object ID 1218103380, index ID 5 will be rebuilt.
>
|||This should process should work fine. What builds are the servers on? SP3a
or above and having the same build number on both servers will probably make
these go away.
"Angie" <NoSpam_angie_kong@.hotmail.NoSpam.com> wrote in message
news:OPpLxmYwFHA.908@.tk2msftngp13.phx.gbl...
> Hi all,
> I am testing SQL Server 2000 64-bit on Itanium2 and have hit a problem.
> Our current production system is running SQL Server 2000 32-bit SP3a. I
> backed up the database (about 200+ GB) and restored it on SQL Server 2000
> 64-bit. After the restore was completed, I did a dbcc_checkdb and it came
> back with various errors (see below for sample). I repeated the restore
> from the same backup on another 32-bit box and dbcc checkdb came out
> clean. Any idea what's causing the errors in dbcc checkdb on the 64-bit
> restore? They're fixable using the repair option but it takes a long time
> and it isn't really inspiring confidence in our management.
> Btw, OS on both is Windows Server 2003 Enterprise SP1.
> Any help will be much appreciated.
> Thanks!
> aK.
>
> Small snippet of error messages:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:76) with values (DetailActivityCurID = 55833475 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:77) with values (DetailActivityCurID = 55833476 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:78) with values (DetailActivityCurID = 55833477 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:79) with values (DetailActivityCurID = 55833478 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:155) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = NULL) points to
> the data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:160) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = 1) points to the
> data row identified by ().
> Server: Msg 8945, Level 16, State 1, Line 1
> Table error: Object ID 1218103380, index ID 5 will be rebuilt.
>
64-bit restore with error
Hi all,
I am testing SQL Server 2000 64-bit on Itanium2 and have hit a problem.
Our current production system is running SQL Server 2000 32-bit SP3a. I
backed up the database (about 200+ GB) and restored it on SQL Server 2000
64-bit. After the restore was completed, I did a dbcc_checkdb and it came
back with various errors (see below for sample). I repeated the restore from
the same backup on another 32-bit box and dbcc checkdb came out clean. Any
idea what's causing the errors in dbcc checkdb on the 64-bit restore?
They're fixable using the repair option but it takes a long time and it
isn't really inspiring confidence in our management.
Btw, OS on both is Windows Server 2003 Enterprise SP1.
Any help will be much appreciated.
Thanks!
aK.
Small snippet of error messages:
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:76) with values (DetailActivityCurID = 55833475 and
WorkorderCurID = 316630 and SetTypeID = 4869 and ? = NULL) points to the
data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:77) with values (DetailActivityCurID = 55833476 and
WorkorderCurID = 316630 and SetTypeID = 4870 and ? = NULL) points to the
data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:78) with values (DetailActivityCurID = 55833477 and
WorkorderCurID = 316630 and SetTypeID = 4869 and ? = 1) points to the data
row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:79) with values (DetailActivityCurID = 55833478 and
WorkorderCurID = 316630 and SetTypeID = 4870 and ? = 1) points to the data
row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
(ID 1218103380) (index ID 4). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4447340:155) with values (ActivityDtime = Jul 14 2005 4:47PM
and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = NULL) points to the
data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
(ID 1218103380) (index ID 4). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4447340:160) with values (ActivityDtime = Jul 14 2005 4:47PM
and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = 1) points to the
data row identified by ().
Server: Msg 8945, Level 16, State 1, Line 1
Table error: Object ID 1218103380, index ID 5 will be rebuilt.Hi
This looks like:
http://support.microsoft.com/defaul...kb;en-us;884856
You may want to upgrade the 32 bit edition to SP4 and then migrate (to the
same version).
John
"Angie" <NoSpam_angie_kong@.hotmail.NoSpam.com> wrote in message
news:OPpLxmYwFHA.908@.tk2msftngp13.phx.gbl...
> Hi all,
> I am testing SQL Server 2000 64-bit on Itanium2 and have hit a problem.
> Our current production system is running SQL Server 2000 32-bit SP3a. I
> backed up the database (about 200+ GB) and restored it on SQL Server 2000
> 64-bit. After the restore was completed, I did a dbcc_checkdb and it came
> back with various errors (see below for sample). I repeated the restore
> from the same backup on another 32-bit box and dbcc checkdb came out
> clean. Any idea what's causing the errors in dbcc checkdb on the 64-bit
> restore? They're fixable using the repair option but it takes a long time
> and it isn't really inspiring confidence in our management.
> Btw, OS on both is Windows Server 2003 Enterprise SP1.
> Any help will be much appreciated.
> Thanks!
> aK.
>
> Small snippet of error messages:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:76) with values (DetailActivityCurID = 55833475 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:77) with values (DetailActivityCurID = 55833476 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:78) with values (DetailActivityCurID = 55833477 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:79) with values (DetailActivityCurID = 55833478 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:155) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = NULL) points to
> the data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:160) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = 1) points to the
> data row identified by ().
> Server: Msg 8945, Level 16, State 1, Line 1
> Table error: Object ID 1218103380, index ID 5 will be rebuilt.
>|||This should process should work fine. What builds are the servers on? SP3a
or above and having the same build number on both servers will probably make
these go away.
"Angie" <NoSpam_angie_kong@.hotmail.NoSpam.com> wrote in message
news:OPpLxmYwFHA.908@.tk2msftngp13.phx.gbl...
> Hi all,
> I am testing SQL Server 2000 64-bit on Itanium2 and have hit a problem.
> Our current production system is running SQL Server 2000 32-bit SP3a. I
> backed up the database (about 200+ GB) and restored it on SQL Server 2000
> 64-bit. After the restore was completed, I did a dbcc_checkdb and it came
> back with various errors (see below for sample). I repeated the restore
> from the same backup on another 32-bit box and dbcc checkdb came out
> clean. Any idea what's causing the errors in dbcc checkdb on the 64-bit
> restore? They're fixable using the repair option but it takes a long time
> and it isn't really inspiring confidence in our management.
> Btw, OS on both is Windows Server 2003 Enterprise SP1.
> Any help will be much appreciated.
> Thanks!
> aK.
>
> Small snippet of error messages:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:76) with values (DetailActivityCurID = 55833475 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:77) with values (DetailActivityCurID = 55833476 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:78) with values (DetailActivityCurID = 55833477 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:79) with values (DetailActivityCurID = 55833478 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:155) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = NULL) points to
> the data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:160) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = 1) points to the
> data row identified by ().
> Server: Msg 8945, Level 16, State 1, Line 1
> Table error: Object ID 1218103380, index ID 5 will be rebuilt.
>
I am testing SQL Server 2000 64-bit on Itanium2 and have hit a problem.
Our current production system is running SQL Server 2000 32-bit SP3a. I
backed up the database (about 200+ GB) and restored it on SQL Server 2000
64-bit. After the restore was completed, I did a dbcc_checkdb and it came
back with various errors (see below for sample). I repeated the restore from
the same backup on another 32-bit box and dbcc checkdb came out clean. Any
idea what's causing the errors in dbcc checkdb on the 64-bit restore?
They're fixable using the repair option but it takes a long time and it
isn't really inspiring confidence in our management.
Btw, OS on both is Windows Server 2003 Enterprise SP1.
Any help will be much appreciated.
Thanks!
aK.
Small snippet of error messages:
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:76) with values (DetailActivityCurID = 55833475 and
WorkorderCurID = 316630 and SetTypeID = 4869 and ? = NULL) points to the
data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:77) with values (DetailActivityCurID = 55833476 and
WorkorderCurID = 316630 and SetTypeID = 4870 and ? = NULL) points to the
data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:78) with values (DetailActivityCurID = 55833477 and
WorkorderCurID = 316630 and SetTypeID = 4869 and ? = 1) points to the data
row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:79) with values (DetailActivityCurID = 55833478 and
WorkorderCurID = 316630 and SetTypeID = 4870 and ? = 1) points to the data
row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
(ID 1218103380) (index ID 4). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4447340:155) with values (ActivityDtime = Jul 14 2005 4:47PM
and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = NULL) points to the
data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
(ID 1218103380) (index ID 4). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4447340:160) with values (ActivityDtime = Jul 14 2005 4:47PM
and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = 1) points to the
data row identified by ().
Server: Msg 8945, Level 16, State 1, Line 1
Table error: Object ID 1218103380, index ID 5 will be rebuilt.Hi
This looks like:
http://support.microsoft.com/defaul...kb;en-us;884856
You may want to upgrade the 32 bit edition to SP4 and then migrate (to the
same version).
John
"Angie" <NoSpam_angie_kong@.hotmail.NoSpam.com> wrote in message
news:OPpLxmYwFHA.908@.tk2msftngp13.phx.gbl...
> Hi all,
> I am testing SQL Server 2000 64-bit on Itanium2 and have hit a problem.
> Our current production system is running SQL Server 2000 32-bit SP3a. I
> backed up the database (about 200+ GB) and restored it on SQL Server 2000
> 64-bit. After the restore was completed, I did a dbcc_checkdb and it came
> back with various errors (see below for sample). I repeated the restore
> from the same backup on another 32-bit box and dbcc checkdb came out
> clean. Any idea what's causing the errors in dbcc checkdb on the 64-bit
> restore? They're fixable using the repair option but it takes a long time
> and it isn't really inspiring confidence in our management.
> Btw, OS on both is Windows Server 2003 Enterprise SP1.
> Any help will be much appreciated.
> Thanks!
> aK.
>
> Small snippet of error messages:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:76) with values (DetailActivityCurID = 55833475 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:77) with values (DetailActivityCurID = 55833476 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:78) with values (DetailActivityCurID = 55833477 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:79) with values (DetailActivityCurID = 55833478 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:155) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = NULL) points to
> the data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:160) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = 1) points to the
> data row identified by ().
> Server: Msg 8945, Level 16, State 1, Line 1
> Table error: Object ID 1218103380, index ID 5 will be rebuilt.
>|||This should process should work fine. What builds are the servers on? SP3a
or above and having the same build number on both servers will probably make
these go away.
"Angie" <NoSpam_angie_kong@.hotmail.NoSpam.com> wrote in message
news:OPpLxmYwFHA.908@.tk2msftngp13.phx.gbl...
> Hi all,
> I am testing SQL Server 2000 64-bit on Itanium2 and have hit a problem.
> Our current production system is running SQL Server 2000 32-bit SP3a. I
> backed up the database (about 200+ GB) and restored it on SQL Server 2000
> 64-bit. After the restore was completed, I did a dbcc_checkdb and it came
> back with various errors (see below for sample). I repeated the restore
> from the same backup on another 32-bit box and dbcc checkdb came out
> clean. Any idea what's causing the errors in dbcc checkdb on the 64-bit
> restore? They're fixable using the repair option but it takes a long time
> and it isn't really inspiring confidence in our management.
> Btw, OS on both is Windows Server 2003 Enterprise SP1.
> Any help will be much appreciated.
> Thanks!
> aK.
>
> Small snippet of error messages:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:76) with values (DetailActivityCurID = 55833475 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:77) with values (DetailActivityCurID = 55833476 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:78) with values (DetailActivityCurID = 55833477 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:79) with values (DetailActivityCurID = 55833478 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:155) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = NULL) points to
> the data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:160) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = 1) points to the
> data row identified by ().
> Server: Msg 8945, Level 16, State 1, Line 1
> Table error: Object ID 1218103380, index ID 5 will be rebuilt.
>
64-bit restore with error
Hi all,
I am testing SQL Server 2000 64-bit on Itanium2 and have hit a problem.
Our current production system is running SQL Server 2000 32-bit SP3a. I
backed up the database (about 200+ GB) and restored it on SQL Server 2000
64-bit. After the restore was completed, I did a dbcc_checkdb and it came
back with various errors (see below for sample). I repeated the restore from
the same backup on another 32-bit box and dbcc checkdb came out clean. Any
idea what's causing the errors in dbcc checkdb on the 64-bit restore?
They're fixable using the repair option but it takes a long time and it
isn't really inspiring confidence in our management.
Btw, OS on both is Windows Server 2003 Enterprise SP1.
Any help will be much appreciated.
Thanks!
aK.
Small snippet of error messages:
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:76) with values (DetailActivityCurID = 55833475 and
WorkorderCurID = 316630 and SetTypeID = 4869 and ? = NULL) points to the
data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:77) with values (DetailActivityCurID = 55833476 and
WorkorderCurID = 316630 and SetTypeID = 4870 and ? = NULL) points to the
data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:78) with values (DetailActivityCurID = 55833477 and
WorkorderCurID = 316630 and SetTypeID = 4869 and ? = 1) points to the data
row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:79) with values (DetailActivityCurID = 55833478 and
WorkorderCurID = 316630 and SetTypeID = 4870 and ? = 1) points to the data
row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
(ID 1218103380) (index ID 4). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4447340:155) with values (ActivityDtime = Jul 14 2005 4:47PM
and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = NULL) points to the
data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
(ID 1218103380) (index ID 4). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4447340:160) with values (ActivityDtime = Jul 14 2005 4:47PM
and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = 1) points to the
data row identified by ().
Server: Msg 8945, Level 16, State 1, Line 1
Table error: Object ID 1218103380, index ID 5 will be rebuilt.Hi
This looks like:
http://support.microsoft.com/default.aspx?scid=kb;en-us;884856
You may want to upgrade the 32 bit edition to SP4 and then migrate (to the
same version).
John
"Angie" <NoSpam_angie_kong@.hotmail.NoSpam.com> wrote in message
news:OPpLxmYwFHA.908@.tk2msftngp13.phx.gbl...
> Hi all,
> I am testing SQL Server 2000 64-bit on Itanium2 and have hit a problem.
> Our current production system is running SQL Server 2000 32-bit SP3a. I
> backed up the database (about 200+ GB) and restored it on SQL Server 2000
> 64-bit. After the restore was completed, I did a dbcc_checkdb and it came
> back with various errors (see below for sample). I repeated the restore
> from the same backup on another 32-bit box and dbcc checkdb came out
> clean. Any idea what's causing the errors in dbcc checkdb on the 64-bit
> restore? They're fixable using the repair option but it takes a long time
> and it isn't really inspiring confidence in our management.
> Btw, OS on both is Windows Server 2003 Enterprise SP1.
> Any help will be much appreciated.
> Thanks!
> aK.
>
> Small snippet of error messages:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:76) with values (DetailActivityCurID = 55833475 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:77) with values (DetailActivityCurID = 55833476 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:78) with values (DetailActivityCurID = 55833477 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:79) with values (DetailActivityCurID = 55833478 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:155) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = NULL) points to
> the data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:160) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = 1) points to the
> data row identified by ().
> Server: Msg 8945, Level 16, State 1, Line 1
> Table error: Object ID 1218103380, index ID 5 will be rebuilt.
>|||This should process should work fine. What builds are the servers on? SP3a
or above and having the same build number on both servers will probably make
these go away.
"Angie" <NoSpam_angie_kong@.hotmail.NoSpam.com> wrote in message
news:OPpLxmYwFHA.908@.tk2msftngp13.phx.gbl...
> Hi all,
> I am testing SQL Server 2000 64-bit on Itanium2 and have hit a problem.
> Our current production system is running SQL Server 2000 32-bit SP3a. I
> backed up the database (about 200+ GB) and restored it on SQL Server 2000
> 64-bit. After the restore was completed, I did a dbcc_checkdb and it came
> back with various errors (see below for sample). I repeated the restore
> from the same backup on another 32-bit box and dbcc checkdb came out
> clean. Any idea what's causing the errors in dbcc checkdb on the 64-bit
> restore? They're fixable using the repair option but it takes a long time
> and it isn't really inspiring confidence in our management.
> Btw, OS on both is Windows Server 2003 Enterprise SP1.
> Any help will be much appreciated.
> Thanks!
> aK.
>
> Small snippet of error messages:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:76) with values (DetailActivityCurID = 55833475 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:77) with values (DetailActivityCurID = 55833476 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:78) with values (DetailActivityCurID = 55833477 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:79) with values (DetailActivityCurID = 55833478 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:155) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = NULL) points to
> the data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:160) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = 1) points to the
> data row identified by ().
> Server: Msg 8945, Level 16, State 1, Line 1
> Table error: Object ID 1218103380, index ID 5 will be rebuilt.
>
I am testing SQL Server 2000 64-bit on Itanium2 and have hit a problem.
Our current production system is running SQL Server 2000 32-bit SP3a. I
backed up the database (about 200+ GB) and restored it on SQL Server 2000
64-bit. After the restore was completed, I did a dbcc_checkdb and it came
back with various errors (see below for sample). I repeated the restore from
the same backup on another 32-bit box and dbcc checkdb came out clean. Any
idea what's causing the errors in dbcc checkdb on the 64-bit restore?
They're fixable using the repair option but it takes a long time and it
isn't really inspiring confidence in our management.
Btw, OS on both is Windows Server 2003 Enterprise SP1.
Any help will be much appreciated.
Thanks!
aK.
Small snippet of error messages:
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:76) with values (DetailActivityCurID = 55833475 and
WorkorderCurID = 316630 and SetTypeID = 4869 and ? = NULL) points to the
data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:77) with values (DetailActivityCurID = 55833476 and
WorkorderCurID = 316630 and SetTypeID = 4870 and ? = NULL) points to the
data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:78) with values (DetailActivityCurID = 55833477 and
WorkorderCurID = 316630 and SetTypeID = 4869 and ? = 1) points to the data
row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index
'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4242635:79) with values (DetailActivityCurID = 55833478 and
WorkorderCurID = 316630 and SetTypeID = 4870 and ? = 1) points to the data
row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
(ID 1218103380) (index ID 4). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4447340:155) with values (ActivityDtime = Jul 14 2005 4:47PM
and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = NULL) points to the
data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
(ID 1218103380) (index ID 4). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4447340:160) with values (ActivityDtime = Jul 14 2005 4:47PM
and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = 1) points to the
data row identified by ().
Server: Msg 8945, Level 16, State 1, Line 1
Table error: Object ID 1218103380, index ID 5 will be rebuilt.Hi
This looks like:
http://support.microsoft.com/default.aspx?scid=kb;en-us;884856
You may want to upgrade the 32 bit edition to SP4 and then migrate (to the
same version).
John
"Angie" <NoSpam_angie_kong@.hotmail.NoSpam.com> wrote in message
news:OPpLxmYwFHA.908@.tk2msftngp13.phx.gbl...
> Hi all,
> I am testing SQL Server 2000 64-bit on Itanium2 and have hit a problem.
> Our current production system is running SQL Server 2000 32-bit SP3a. I
> backed up the database (about 200+ GB) and restored it on SQL Server 2000
> 64-bit. After the restore was completed, I did a dbcc_checkdb and it came
> back with various errors (see below for sample). I repeated the restore
> from the same backup on another 32-bit box and dbcc checkdb came out
> clean. Any idea what's causing the errors in dbcc checkdb on the 64-bit
> restore? They're fixable using the repair option but it takes a long time
> and it isn't really inspiring confidence in our management.
> Btw, OS on both is Windows Server 2003 Enterprise SP1.
> Any help will be much appreciated.
> Thanks!
> aK.
>
> Small snippet of error messages:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:76) with values (DetailActivityCurID = 55833475 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:77) with values (DetailActivityCurID = 55833476 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:78) with values (DetailActivityCurID = 55833477 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:79) with values (DetailActivityCurID = 55833478 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:155) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = NULL) points to
> the data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:160) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = 1) points to the
> data row identified by ().
> Server: Msg 8945, Level 16, State 1, Line 1
> Table error: Object ID 1218103380, index ID 5 will be rebuilt.
>|||This should process should work fine. What builds are the servers on? SP3a
or above and having the same build number on both servers will probably make
these go away.
"Angie" <NoSpam_angie_kong@.hotmail.NoSpam.com> wrote in message
news:OPpLxmYwFHA.908@.tk2msftngp13.phx.gbl...
> Hi all,
> I am testing SQL Server 2000 64-bit on Itanium2 and have hit a problem.
> Our current production system is running SQL Server 2000 32-bit SP3a. I
> backed up the database (about 200+ GB) and restored it on SQL Server 2000
> 64-bit. After the restore was completed, I did a dbcc_checkdb and it came
> back with various errors (see below for sample). I repeated the restore
> from the same backup on another 32-bit box and dbcc checkdb came out
> clean. Any idea what's causing the errors in dbcc checkdb on the 64-bit
> restore? They're fixable using the repair option but it takes a long time
> and it isn't really inspiring confidence in our management.
> Btw, OS on both is Windows Server 2003 Enterprise SP1.
> Any help will be much appreciated.
> Thanks!
> aK.
>
> Small snippet of error messages:
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:76) with values (DetailActivityCurID = 55833475 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:77) with values (DetailActivityCurID = 55833476 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = NULL) points to the
> data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:78) with values (DetailActivityCurID = 55833477 and
> WorkorderCurID = 316630 and SetTypeID = 4869 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index
> 'DetailActivityCur.pkDetailActivityCur_ID' (ID 1218103380) (index ID 2).
> Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4242635:79) with values (DetailActivityCurID = 55833478 and
> WorkorderCurID = 316630 and SetTypeID = 4870 and ? = 1) points to the data
> row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:155) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = NULL) points to
> the data row identified by ().
> Server: Msg 8952, Level 16, State 1, Line 1
> Table error: Database 'RSTBL1', index 'DetailActivityCur.akActivityDtime'
> (ID 1218103380) (index ID 4). Extra or invalid key for the keys:
> Server: Msg 8956, Level 16, State 1, Line 1
> Index row (1:4447340:160) with values (ActivityDtime = Jul 14 2005 4:47PM
> and WorkorderCurID = 316630 and SetTypeID = 4868 and ? = 1) points to the
> data row identified by ().
> Server: Msg 8945, Level 16, State 1, Line 1
> Table error: Object ID 1218103380, index ID 5 will be rebuilt.
>
64-bit Restore via 32-bit GUI
Hello all,
I'm trying to use the 32-bit GUI, on a remote server, to restore a database
on one of our 64-bit servers. The GUI returns a prompt that the restore was
successful but the GUI indicates that the database is in a Loading mode. I
tried to issue a recovery command but it fails saying that some of the files
were partially restored.
I figured that there is a problem using the 32-bit client utility so I used
OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
compatible 64-bit utility. By doing so, I was able to restore the database
successfully.
So my question is, is not being able to restore a 64-bit database via a
32-bit GUI, on a remote server, a known issue?
Thanks...Not that I'm aware of. EM is simply building the restore command and
sending it to the server. Try it again with EM but capture the command with
profiler. You can then determine if the command generated is good. Did you
change the recovery to Leave database nonoperational?
"BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
news:CA08652F-A880-48E8-A03B-1567EE5145A6@.microsoft.com...
> Hello all,
> I'm trying to use the 32-bit GUI, on a remote server, to restore a
> database
> on one of our 64-bit servers. The GUI returns a prompt that the restore
> was
> successful but the GUI indicates that the database is in a Loading mode.
> I
> tried to issue a recovery command but it fails saying that some of the
> files
> were partially restored.
> I figured that there is a problem using the 32-bit client utility so I
> used
> OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
> compatible 64-bit utility. By doing so, I was able to restore the
> database
> successfully.
> So my question is, is not being able to restore a 64-bit database via a
> 32-bit GUI, on a remote server, a known issue?
> Thanks...
>
I'm trying to use the 32-bit GUI, on a remote server, to restore a database
on one of our 64-bit servers. The GUI returns a prompt that the restore was
successful but the GUI indicates that the database is in a Loading mode. I
tried to issue a recovery command but it fails saying that some of the files
were partially restored.
I figured that there is a problem using the 32-bit client utility so I used
OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
compatible 64-bit utility. By doing so, I was able to restore the database
successfully.
So my question is, is not being able to restore a 64-bit database via a
32-bit GUI, on a remote server, a known issue?
Thanks...Not that I'm aware of. EM is simply building the restore command and
sending it to the server. Try it again with EM but capture the command with
profiler. You can then determine if the command generated is good. Did you
change the recovery to Leave database nonoperational?
"BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
news:CA08652F-A880-48E8-A03B-1567EE5145A6@.microsoft.com...
> Hello all,
> I'm trying to use the 32-bit GUI, on a remote server, to restore a
> database
> on one of our 64-bit servers. The GUI returns a prompt that the restore
> was
> successful but the GUI indicates that the database is in a Loading mode.
> I
> tried to issue a recovery command but it fails saying that some of the
> files
> were partially restored.
> I figured that there is a problem using the 32-bit client utility so I
> used
> OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
> compatible 64-bit utility. By doing so, I was able to restore the
> database
> successfully.
> So my question is, is not being able to restore a 64-bit database via a
> 32-bit GUI, on a remote server, a known issue?
> Thanks...
>
64-bit Restore via 32-bit GUI
Hello all,
I'm trying to use the 32-bit GUI, on a remote server, to restore a database
on one of our 64-bit servers. The GUI returns a prompt that the restore was
successful but the GUI indicates that the database is in a Loading mode. I
tried to issue a recovery command but it fails saying that some of the files
were partially restored.
I figured that there is a problem using the 32-bit client utility so I used
OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
compatible 64-bit utility. By doing so, I was able to restore the database
successfully.
So my question is, is not being able to restore a 64-bit database via a
32-bit GUI, on a remote server, a known issue?
Thanks...
Not that I'm aware of. EM is simply building the restore command and
sending it to the server. Try it again with EM but capture the command with
profiler. You can then determine if the command generated is good. Did you
change the recovery to Leave database nonoperational?
"BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
news:CA08652F-A880-48E8-A03B-1567EE5145A6@.microsoft.com...
> Hello all,
> I'm trying to use the 32-bit GUI, on a remote server, to restore a
> database
> on one of our 64-bit servers. The GUI returns a prompt that the restore
> was
> successful but the GUI indicates that the database is in a Loading mode.
> I
> tried to issue a recovery command but it fails saying that some of the
> files
> were partially restored.
> I figured that there is a problem using the 32-bit client utility so I
> used
> OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
> compatible 64-bit utility. By doing so, I was able to restore the
> database
> successfully.
> So my question is, is not being able to restore a 64-bit database via a
> 32-bit GUI, on a remote server, a known issue?
> Thanks...
>
I'm trying to use the 32-bit GUI, on a remote server, to restore a database
on one of our 64-bit servers. The GUI returns a prompt that the restore was
successful but the GUI indicates that the database is in a Loading mode. I
tried to issue a recovery command but it fails saying that some of the files
were partially restored.
I figured that there is a problem using the 32-bit client utility so I used
OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
compatible 64-bit utility. By doing so, I was able to restore the database
successfully.
So my question is, is not being able to restore a 64-bit database via a
32-bit GUI, on a remote server, a known issue?
Thanks...
Not that I'm aware of. EM is simply building the restore command and
sending it to the server. Try it again with EM but capture the command with
profiler. You can then determine if the command generated is good. Did you
change the recovery to Leave database nonoperational?
"BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
news:CA08652F-A880-48E8-A03B-1567EE5145A6@.microsoft.com...
> Hello all,
> I'm trying to use the 32-bit GUI, on a remote server, to restore a
> database
> on one of our 64-bit servers. The GUI returns a prompt that the restore
> was
> successful but the GUI indicates that the database is in a Loading mode.
> I
> tried to issue a recovery command but it fails saying that some of the
> files
> were partially restored.
> I figured that there is a problem using the 32-bit client utility so I
> used
> OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
> compatible 64-bit utility. By doing so, I was able to restore the
> database
> successfully.
> So my question is, is not being able to restore a 64-bit database via a
> 32-bit GUI, on a remote server, a known issue?
> Thanks...
>
64-bit Restore via 32-bit GUI
Hello all,
I'm trying to use the 32-bit GUI, on a remote server, to restore a database
on one of our 64-bit servers. The GUI returns a prompt that the restore was
successful but the GUI indicates that the database is in a Loading mode. I
tried to issue a recovery command but it fails saying that some of the files
were partially restored.
I figured that there is a problem using the 32-bit client utility so I used
OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
compatible 64-bit utility. By doing so, I was able to restore the database
successfully.
So my question is, is not being able to restore a 64-bit database via a
32-bit GUI, on a remote server, a known issue?
Thanks...Not that I'm aware of. EM is simply building the restore command and
sending it to the server. Try it again with EM but capture the command with
profiler. You can then determine if the command generated is good. Did you
change the recovery to Leave database nonoperational?
"BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
news:CA08652F-A880-48E8-A03B-1567EE5145A6@.microsoft.com...
> Hello all,
> I'm trying to use the 32-bit GUI, on a remote server, to restore a
> database
> on one of our 64-bit servers. The GUI returns a prompt that the restore
> was
> successful but the GUI indicates that the database is in a Loading mode.
> I
> tried to issue a recovery command but it fails saying that some of the
> files
> were partially restored.
> I figured that there is a problem using the 32-bit client utility so I
> used
> OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
> compatible 64-bit utility. By doing so, I was able to restore the
> database
> successfully.
> So my question is, is not being able to restore a 64-bit database via a
> 32-bit GUI, on a remote server, a known issue?
> Thanks...
>
I'm trying to use the 32-bit GUI, on a remote server, to restore a database
on one of our 64-bit servers. The GUI returns a prompt that the restore was
successful but the GUI indicates that the database is in a Loading mode. I
tried to issue a recovery command but it fails saying that some of the files
were partially restored.
I figured that there is a problem using the 32-bit client utility so I used
OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
compatible 64-bit utility. By doing so, I was able to restore the database
successfully.
So my question is, is not being able to restore a 64-bit database via a
32-bit GUI, on a remote server, a known issue?
Thanks...Not that I'm aware of. EM is simply building the restore command and
sending it to the server. Try it again with EM but capture the command with
profiler. You can then determine if the command generated is good. Did you
change the recovery to Leave database nonoperational?
"BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
news:CA08652F-A880-48E8-A03B-1567EE5145A6@.microsoft.com...
> Hello all,
> I'm trying to use the 32-bit GUI, on a remote server, to restore a
> database
> on one of our 64-bit servers. The GUI returns a prompt that the restore
> was
> successful but the GUI indicates that the database is in a Loading mode.
> I
> tried to issue a recovery command but it fails saying that some of the
> files
> were partially restored.
> I figured that there is a problem using the 32-bit client utility so I
> used
> OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
> compatible 64-bit utility. By doing so, I was able to restore the
> database
> successfully.
> So my question is, is not being able to restore a 64-bit database via a
> 32-bit GUI, on a remote server, a known issue?
> Thanks...
>
Sunday, February 19, 2012
6.5 to 2K Restore
Hello:
Is there anyway to restore a SQL 6.5 database backup
directly into a SQL 2000 DB?
Thanks
BrennanNo. You must go thru the upgrade path which means you first need to restore
to a 6.5 machine.
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/sql/deploy/upgrdmigrate/sqlugrd.asp
Andrew J. Kelly
SQL Server MVP
"Brennan" <anonymous@.discussions.microsoft.com> wrote in message
news:0c0d01c39442$9edb9950$a001280a@.phx.gbl...
> Hello:
> Is there anyway to restore a SQL 6.5 database backup
> directly into a SQL 2000 DB?
> Thanks
> Brennan
Is there anyway to restore a SQL 6.5 database backup
directly into a SQL 2000 DB?
Thanks
BrennanNo. You must go thru the upgrade path which means you first need to restore
to a 6.5 machine.
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/sql/deploy/upgrdmigrate/sqlugrd.asp
Andrew J. Kelly
SQL Server MVP
"Brennan" <anonymous@.discussions.microsoft.com> wrote in message
news:0c0d01c39442$9edb9950$a001280a@.phx.gbl...
> Hello:
> Is there anyway to restore a SQL 6.5 database backup
> directly into a SQL 2000 DB?
> Thanks
> Brennan
6.5 Restore
Hi all,
I'm trying to move a SQL Server 6.5 database from one almost extinct NT4 box, to a whizz-bang only-almost-dead NT4 box. These boxes live in different domains, and CANNOT be networked together.
The original box has a daily backup routine that runs daily, with no errors. A colleague copied the data, log files and a single backup file from the overnight job from the original box, to the "new" box over the weekend, but when I go to restore the database from the backup file, the new installation doesn't seem to recognise a backup within this file. We have a backup file from that database that is about 2 years old, which restores perfectly well, but obviously, doesn't quite meet our needs data wise.
Is there an sp_attachdb (or equivalent) in SQL Server 6.5 that I can use to create a new database with the orignal data and log file??You can do something like sp_attach_db, but in SQL 6.5 it is pure smoke-and-mirrors, and almost completely unsupported.
Before we even head down that path, the problem you describe was common when trying to install a backup made with a later service pack than the machine trying to do the restore. As an example, if you made a backup with sp6 then tried to restore it using RTM (or even sp4) the server wouldn't even recognize it as a backup file, much less actually restore it!
My advice is to find out what service pack was applied to the machine making the backup, then bring the machine doing the restore to the same (or later) service pack.
-PatP|||Thanks Pat.
I've just checked and both machines are showing...
Microsoft SQL Server 6.50 - 6.50.416 (Intel X86)
Jan 23 1999 14:10:24
Also, the backup I CAN restore to the "new" box comes from the same original box as the backup that is unrecognised (admittedly some time ago, and therefore possibly some SP's ago)
The backup I can't restore on the new box, doesn't show any Backup Information in the "Add file" window of the restore options. On the original server however, the Backup Information shows just fine.
Is the create using original data and log files option really not advisable??
Thanks in advance
zinedunc|||Is the create using original data and log files option really not advisable??I would only try to attach a 6.5 database on a server that was 100% expendable, one that I didn't care if I had to reinstall both NT and SQL if necessary.
Have you tried using the LOAD DATABASE command from ISQL/W to see what results it returns?
-PatP|||I haven't tried that yet Pat - I've had very little experience on 6.5, and any 6.5 restores I've done in the past have been via the standard restore from backup files, without any issues.
I only have a backup file (created by a scheduled Backup Device, which the "new" server doesn't seem to like) and the original data and log files (copied from the original server when SQL Server service was stopped) - which of these, if any, can be used in the LOAD DATABASE statement please??|||i don't know if this is possible, but could you bcp out all the tables and data individually and then bcp them into a fresh datbase on the "new" box? it would take an age, but i think it could be done.|||Is this a problem of the database will not restore, or a problem of SQL Server can not "read" the backup file? Try running this:
restore headeronly from disk = 'your backup file'
Been a while since I used 6.5, so it may be "load headeronly" as opposed to "restore headeronly".
This command will only read the header information from the backup file, so you can see what is in it.|||Thanks to Pat, cruickshanks and MCrowley for your suggestions.
"load headeronly" using the backup file proved that SQL Server could read the file, and I currently have a "load database" command running against that file, that after an hour or so (thankfully) has not returned any errors.
Here's hoping all is well in the morning.
Thanks again.|||Ah, the "load database" I left running overnight didn't work.
I didn't receive an error as such, but got the following message returned....
"This command did not return any data, and it did not return any rows"
The original box here is not on site, and cannot be accessed from my network, so it's not as simple as taking another backup and copying it across.
Any ideas what else I can try with this backup file, or the original data and log files to save me a 200 mile drive today??
Thanks in advance|||Ah, OK, panic over....
The data appears to be in place, am just waiting for confirmation following testing through the application.
Thanks for all your help|||Sorry, we should have warned you that "no rows returned" was the expected response. It's been a while since I've used 6.5 on any regular basis, so I don't always think to forewarn people about its quirks.
-PatP
I'm trying to move a SQL Server 6.5 database from one almost extinct NT4 box, to a whizz-bang only-almost-dead NT4 box. These boxes live in different domains, and CANNOT be networked together.
The original box has a daily backup routine that runs daily, with no errors. A colleague copied the data, log files and a single backup file from the overnight job from the original box, to the "new" box over the weekend, but when I go to restore the database from the backup file, the new installation doesn't seem to recognise a backup within this file. We have a backup file from that database that is about 2 years old, which restores perfectly well, but obviously, doesn't quite meet our needs data wise.
Is there an sp_attachdb (or equivalent) in SQL Server 6.5 that I can use to create a new database with the orignal data and log file??You can do something like sp_attach_db, but in SQL 6.5 it is pure smoke-and-mirrors, and almost completely unsupported.
Before we even head down that path, the problem you describe was common when trying to install a backup made with a later service pack than the machine trying to do the restore. As an example, if you made a backup with sp6 then tried to restore it using RTM (or even sp4) the server wouldn't even recognize it as a backup file, much less actually restore it!
My advice is to find out what service pack was applied to the machine making the backup, then bring the machine doing the restore to the same (or later) service pack.
-PatP|||Thanks Pat.
I've just checked and both machines are showing...
Microsoft SQL Server 6.50 - 6.50.416 (Intel X86)
Jan 23 1999 14:10:24
Also, the backup I CAN restore to the "new" box comes from the same original box as the backup that is unrecognised (admittedly some time ago, and therefore possibly some SP's ago)
The backup I can't restore on the new box, doesn't show any Backup Information in the "Add file" window of the restore options. On the original server however, the Backup Information shows just fine.
Is the create using original data and log files option really not advisable??
Thanks in advance
zinedunc|||Is the create using original data and log files option really not advisable??I would only try to attach a 6.5 database on a server that was 100% expendable, one that I didn't care if I had to reinstall both NT and SQL if necessary.
Have you tried using the LOAD DATABASE command from ISQL/W to see what results it returns?
-PatP|||I haven't tried that yet Pat - I've had very little experience on 6.5, and any 6.5 restores I've done in the past have been via the standard restore from backup files, without any issues.
I only have a backup file (created by a scheduled Backup Device, which the "new" server doesn't seem to like) and the original data and log files (copied from the original server when SQL Server service was stopped) - which of these, if any, can be used in the LOAD DATABASE statement please??|||i don't know if this is possible, but could you bcp out all the tables and data individually and then bcp them into a fresh datbase on the "new" box? it would take an age, but i think it could be done.|||Is this a problem of the database will not restore, or a problem of SQL Server can not "read" the backup file? Try running this:
restore headeronly from disk = 'your backup file'
Been a while since I used 6.5, so it may be "load headeronly" as opposed to "restore headeronly".
This command will only read the header information from the backup file, so you can see what is in it.|||Thanks to Pat, cruickshanks and MCrowley for your suggestions.
"load headeronly" using the backup file proved that SQL Server could read the file, and I currently have a "load database" command running against that file, that after an hour or so (thankfully) has not returned any errors.
Here's hoping all is well in the morning.
Thanks again.|||Ah, the "load database" I left running overnight didn't work.
I didn't receive an error as such, but got the following message returned....
"This command did not return any data, and it did not return any rows"
The original box here is not on site, and cannot be accessed from my network, so it's not as simple as taking another backup and copying it across.
Any ideas what else I can try with this backup file, or the original data and log files to save me a 200 mile drive today??
Thanks in advance|||Ah, OK, panic over....
The data appears to be in place, am just waiting for confirmation following testing through the application.
Thanks for all your help|||Sorry, we should have warned you that "no rows returned" was the expected response. It's been a while since I've used 6.5 on any regular basis, so I don't always think to forewarn people about its quirks.
-PatP
Thursday, February 9, 2012
3rd party backup/restore
I'm looking for recommendations for 3rd party backup/restore software for
SQL Server 2000.
The software must be cluster aware. Ease and speed of recoverability are
most important. I am not so concerned with compression ratio but rather the
ease of which junior staff could restore databases at crunch time. Point in
time restore is essential.
thanks to any one who could offer an opinion.
A follow-up if I may. Do any of these products allow you to recovers users
at the server level when a restoring a database to a different server. It's
a hassle scripting and transferring logins.
"Terri" <terri@.cybernets.com> wrote in message
news:f1vj1k$teb$1@.reader2.nmix.net...
> I'm looking for recommendations for 3rd party backup/restore software for
> SQL Server 2000.
> The software must be cluster aware. Ease and speed of recoverability are
> most important. I am not so concerned with compression ratio but rather
the
> ease of which junior staff could restore databases at crunch time. Point
in
> time restore is essential.
> thanks to any one who could offer an opinion.
>
|||"Terri" <terri@.cybernets.com> wrote in message
news:f1vj1k$teb$1@.reader2.nmix.net...
> I'm looking for recommendations for 3rd party backup/restore software for
> SQL Server 2000.
>
Any particular reason you can't use the built in backup tools for SQL Server
2000?
In any case, I'd recommend Litespeed for SQL Server.
> The software must be cluster aware. Ease and speed of recoverability are
> most important. I am not so concerned with compression ratio but rather
> the
> ease of which junior staff could restore databases at crunch time. Point
> in
> time restore is essential.
> thanks to any one who could offer an opinion.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||I am very happy with the price, the speed, and the ease of restores and
backups using RED GATE. Instead of bak sizes of 80+ gig, they are about 10
gig. Its a great piece of software.
Regards,
Jamie
"Terri" wrote:
> A follow-up if I may. Do any of these products allow you to recovers users
> at the server level when a restoring a database to a different server. It's
> a hassle scripting and transferring logins.
>
> "Terri" <terri@.cybernets.com> wrote in message
> news:f1vj1k$teb$1@.reader2.nmix.net...
> the
> in
>
>
|||"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:OURUS2ykHHA.3484@.TK2MSFTNGP02.phx.gbl...[vbcol=seagreen]
>
> "Terri" <terri@.cybernets.com> wrote in message
> news:f1vj1k$teb$1@.reader2.nmix.net...
for
> Any particular reason you can't use the built in backup tools for SQL
Server
> 2000?
I'm hoping it would be easier for an administrator to make a timely restore.
The performance boost can't hurt.
> In any case, I'd recommend Litespeed for SQL Server.
Thanks for your response, I'll take a look.
|||"Terri" <terri@.cybernets.com> wrote in message
news:f2070q$2i9$1@.reader2.nmix.net...
> "Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in
> message
> news:OURUS2ykHHA.3484@.TK2MSFTNGP02.phx.gbl...
> for
> Server
> I'm hoping it would be easier for an administrator to make a timely
> restore.
> The performance boost can't hurt.
Easier?
Can't say I ever found
RESTORE DATABASE FOO from file="backup.bak" with NORECOVERY
all that complex :-)
But.. the performance boost is definitely a plus.
>
> Thanks for your response, I'll take a look.
>
|||Are Red Gate and Lightspeed cluster aware? Also, can those products restore
to a server on which the product does not reside?
Terri, if you REALLY want ease/speed of recoverability, get familiar with
the backupset system table and create a restore database script that takes a
parameter of @.DBName and creates all necessary RESTORE statements to
completely recover a database. Holy-Shit time is NOT the time to be
futzing with an interface you aren't familiar with. I used such a mechanism
(albeit a BIT more complex and hand-crafted at crunch time) earlier this
year to restore 719 databases having 6 backup files each to two different
servers in about 4 hours total time. :-O
TheSQLGuru
President
Indicium Resources, Inc.
"Terri" <terri@.cybernets.com> wrote in message
news:f1vj1k$teb$1@.reader2.nmix.net...
> I'm looking for recommendations for 3rd party backup/restore software for
> SQL Server 2000.
> The software must be cluster aware. Ease and speed of recoverability are
> most important. I am not so concerned with compression ratio but rather
> the
> ease of which junior staff could restore databases at crunch time. Point
> in
> time restore is essential.
> thanks to any one who could offer an opinion.
>
SQL Server 2000.
The software must be cluster aware. Ease and speed of recoverability are
most important. I am not so concerned with compression ratio but rather the
ease of which junior staff could restore databases at crunch time. Point in
time restore is essential.
thanks to any one who could offer an opinion.
A follow-up if I may. Do any of these products allow you to recovers users
at the server level when a restoring a database to a different server. It's
a hassle scripting and transferring logins.
"Terri" <terri@.cybernets.com> wrote in message
news:f1vj1k$teb$1@.reader2.nmix.net...
> I'm looking for recommendations for 3rd party backup/restore software for
> SQL Server 2000.
> The software must be cluster aware. Ease and speed of recoverability are
> most important. I am not so concerned with compression ratio but rather
the
> ease of which junior staff could restore databases at crunch time. Point
in
> time restore is essential.
> thanks to any one who could offer an opinion.
>
|||"Terri" <terri@.cybernets.com> wrote in message
news:f1vj1k$teb$1@.reader2.nmix.net...
> I'm looking for recommendations for 3rd party backup/restore software for
> SQL Server 2000.
>
Any particular reason you can't use the built in backup tools for SQL Server
2000?
In any case, I'd recommend Litespeed for SQL Server.
> The software must be cluster aware. Ease and speed of recoverability are
> most important. I am not so concerned with compression ratio but rather
> the
> ease of which junior staff could restore databases at crunch time. Point
> in
> time restore is essential.
> thanks to any one who could offer an opinion.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||I am very happy with the price, the speed, and the ease of restores and
backups using RED GATE. Instead of bak sizes of 80+ gig, they are about 10
gig. Its a great piece of software.
Regards,
Jamie
"Terri" wrote:
> A follow-up if I may. Do any of these products allow you to recovers users
> at the server level when a restoring a database to a different server. It's
> a hassle scripting and transferring logins.
>
> "Terri" <terri@.cybernets.com> wrote in message
> news:f1vj1k$teb$1@.reader2.nmix.net...
> the
> in
>
>
|||"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:OURUS2ykHHA.3484@.TK2MSFTNGP02.phx.gbl...[vbcol=seagreen]
>
> "Terri" <terri@.cybernets.com> wrote in message
> news:f1vj1k$teb$1@.reader2.nmix.net...
for
> Any particular reason you can't use the built in backup tools for SQL
Server
> 2000?
I'm hoping it would be easier for an administrator to make a timely restore.
The performance boost can't hurt.
> In any case, I'd recommend Litespeed for SQL Server.
Thanks for your response, I'll take a look.
|||"Terri" <terri@.cybernets.com> wrote in message
news:f2070q$2i9$1@.reader2.nmix.net...
> "Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in
> message
> news:OURUS2ykHHA.3484@.TK2MSFTNGP02.phx.gbl...
> for
> Server
> I'm hoping it would be easier for an administrator to make a timely
> restore.
> The performance boost can't hurt.
Easier?
Can't say I ever found
RESTORE DATABASE FOO from file="backup.bak" with NORECOVERY
all that complex :-)
But.. the performance boost is definitely a plus.
>
> Thanks for your response, I'll take a look.
>
|||Are Red Gate and Lightspeed cluster aware? Also, can those products restore
to a server on which the product does not reside?
Terri, if you REALLY want ease/speed of recoverability, get familiar with
the backupset system table and create a restore database script that takes a
parameter of @.DBName and creates all necessary RESTORE statements to
completely recover a database. Holy-Shit time is NOT the time to be
futzing with an interface you aren't familiar with. I used such a mechanism
(albeit a BIT more complex and hand-crafted at crunch time) earlier this
year to restore 719 databases having 6 backup files each to two different
servers in about 4 hours total time. :-O
TheSQLGuru
President
Indicium Resources, Inc.
"Terri" <terri@.cybernets.com> wrote in message
news:f1vj1k$teb$1@.reader2.nmix.net...
> I'm looking for recommendations for 3rd party backup/restore software for
> SQL Server 2000.
> The software must be cluster aware. Ease and speed of recoverability are
> most important. I am not so concerned with compression ratio but rather
> the
> ease of which junior staff could restore databases at crunch time. Point
> in
> time restore is essential.
> thanks to any one who could offer an opinion.
>
3rd party backup/restore
I'm looking for recommendations for 3rd party backup/restore software for
SQL Server 2000.
The software must be cluster aware. Ease and speed of recoverability are
most important. I am not so concerned with compression ratio but rather the
ease of which junior staff could restore databases at crunch time. Point in
time restore is essential.
thanks to any one who could offer an opinion.A follow-up if I may. Do any of these products allow you to recovers users
at the server level when a restoring a database to a different server. It's
a hassle scripting and transferring logins.
"Terri" <terri@.cybernets.com> wrote in message
news:f1vj1k$teb$1@.reader2.nmix.net...
> I'm looking for recommendations for 3rd party backup/restore software for
> SQL Server 2000.
> The software must be cluster aware. Ease and speed of recoverability are
> most important. I am not so concerned with compression ratio but rather
the
> ease of which junior staff could restore databases at crunch time. Point
in
> time restore is essential.
> thanks to any one who could offer an opinion.
>|||"Terri" <terri@.cybernets.com> wrote in message
news:f1vj1k$teb$1@.reader2.nmix.net...
> I'm looking for recommendations for 3rd party backup/restore software for
> SQL Server 2000.
>
Any particular reason you can't use the built in backup tools for SQL Server
2000?
In any case, I'd recommend Litespeed for SQL Server.
> The software must be cluster aware. Ease and speed of recoverability are
> most important. I am not so concerned with compression ratio but rather
> the
> ease of which junior staff could restore databases at crunch time. Point
> in
> time restore is essential.
> thanks to any one who could offer an opinion.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||I am very happy with the price, the speed, and the ease of restores and
backups using RED GATE. Instead of bak sizes of 80+ gig, they are about 10
gig. Its a great piece of software.
--
Regards,
Jamie
"Terri" wrote:
> A follow-up if I may. Do any of these products allow you to recovers users
> at the server level when a restoring a database to a different server. It'
s
> a hassle scripting and transferring logins.
>
> "Terri" <terri@.cybernets.com> wrote in message
> news:f1vj1k$teb$1@.reader2.nmix.net...
> the
> in
>
>|||"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:OURUS2ykHHA.3484@.TK2MSFTNGP02.phx.gbl...
>
> "Terri" <terri@.cybernets.com> wrote in message
> news:f1vj1k$teb$1@.reader2.nmix.net...
for[vbcol=seagreen]
> Any particular reason you can't use the built in backup tools for SQL
Server
> 2000?
I'm hoping it would be easier for an administrator to make a timely restore.
The performance boost can't hurt.
> In any case, I'd recommend Litespeed for SQL Server.
Thanks for your response, I'll take a look.|||"Terri" <terri@.cybernets.com> wrote in message
news:f2070q$2i9$1@.reader2.nmix.net...
> "Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in
> message
> news:OURUS2ykHHA.3484@.TK2MSFTNGP02.phx.gbl...
> for
> Server
> I'm hoping it would be easier for an administrator to make a timely
> restore.
> The performance boost can't hurt.
Easier?
Can't say I ever found
RESTORE DATABASE FOO from file="backup.bak" with NORECOVERY
all that complex :-)
But.. the performance boost is definitely a plus.
>
> Thanks for your response, I'll take a look.
>|||Are Red Gate and Lightspeed cluster aware? Also, can those products restore
to a server on which the product does not reside?
Terri, if you REALLY want ease/speed of recoverability, get familiar with
the backupset system table and create a restore database script that takes a
parameter of @.DBName and creates all necessary RESTORE statements to
completely recover a database. Holy-Shit time is NOT the time to be
futzing with an interface you aren't familiar with. I used such a mechanism
(albeit a BIT more complex and hand-crafted at crunch time) earlier this
year to restore 719 databases having 6 backup files each to two different
servers in about 4 hours total time. :-O
TheSQLGuru
President
Indicium Resources, Inc.
"Terri" <terri@.cybernets.com> wrote in message
news:f1vj1k$teb$1@.reader2.nmix.net...
> I'm looking for recommendations for 3rd party backup/restore software for
> SQL Server 2000.
> The software must be cluster aware. Ease and speed of recoverability are
> most important. I am not so concerned with compression ratio but rather
> the
> ease of which junior staff could restore databases at crunch time. Point
> in
> time restore is essential.
> thanks to any one who could offer an opinion.
>
SQL Server 2000.
The software must be cluster aware. Ease and speed of recoverability are
most important. I am not so concerned with compression ratio but rather the
ease of which junior staff could restore databases at crunch time. Point in
time restore is essential.
thanks to any one who could offer an opinion.A follow-up if I may. Do any of these products allow you to recovers users
at the server level when a restoring a database to a different server. It's
a hassle scripting and transferring logins.
"Terri" <terri@.cybernets.com> wrote in message
news:f1vj1k$teb$1@.reader2.nmix.net...
> I'm looking for recommendations for 3rd party backup/restore software for
> SQL Server 2000.
> The software must be cluster aware. Ease and speed of recoverability are
> most important. I am not so concerned with compression ratio but rather
the
> ease of which junior staff could restore databases at crunch time. Point
in
> time restore is essential.
> thanks to any one who could offer an opinion.
>|||"Terri" <terri@.cybernets.com> wrote in message
news:f1vj1k$teb$1@.reader2.nmix.net...
> I'm looking for recommendations for 3rd party backup/restore software for
> SQL Server 2000.
>
Any particular reason you can't use the built in backup tools for SQL Server
2000?
In any case, I'd recommend Litespeed for SQL Server.
> The software must be cluster aware. Ease and speed of recoverability are
> most important. I am not so concerned with compression ratio but rather
> the
> ease of which junior staff could restore databases at crunch time. Point
> in
> time restore is essential.
> thanks to any one who could offer an opinion.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||I am very happy with the price, the speed, and the ease of restores and
backups using RED GATE. Instead of bak sizes of 80+ gig, they are about 10
gig. Its a great piece of software.
--
Regards,
Jamie
"Terri" wrote:
> A follow-up if I may. Do any of these products allow you to recovers users
> at the server level when a restoring a database to a different server. It'
s
> a hassle scripting and transferring logins.
>
> "Terri" <terri@.cybernets.com> wrote in message
> news:f1vj1k$teb$1@.reader2.nmix.net...
> the
> in
>
>|||"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:OURUS2ykHHA.3484@.TK2MSFTNGP02.phx.gbl...
>
> "Terri" <terri@.cybernets.com> wrote in message
> news:f1vj1k$teb$1@.reader2.nmix.net...
for[vbcol=seagreen]
> Any particular reason you can't use the built in backup tools for SQL
Server
> 2000?
I'm hoping it would be easier for an administrator to make a timely restore.
The performance boost can't hurt.
> In any case, I'd recommend Litespeed for SQL Server.
Thanks for your response, I'll take a look.|||"Terri" <terri@.cybernets.com> wrote in message
news:f2070q$2i9$1@.reader2.nmix.net...
> "Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in
> message
> news:OURUS2ykHHA.3484@.TK2MSFTNGP02.phx.gbl...
> for
> Server
> I'm hoping it would be easier for an administrator to make a timely
> restore.
> The performance boost can't hurt.
Easier?
Can't say I ever found
RESTORE DATABASE FOO from file="backup.bak" with NORECOVERY
all that complex :-)
But.. the performance boost is definitely a plus.
>
> Thanks for your response, I'll take a look.
>|||Are Red Gate and Lightspeed cluster aware? Also, can those products restore
to a server on which the product does not reside?
Terri, if you REALLY want ease/speed of recoverability, get familiar with
the backupset system table and create a restore database script that takes a
parameter of @.DBName and creates all necessary RESTORE statements to
completely recover a database. Holy-Shit time is NOT the time to be
futzing with an interface you aren't familiar with. I used such a mechanism
(albeit a BIT more complex and hand-crafted at crunch time) earlier this
year to restore 719 databases having 6 backup files each to two different
servers in about 4 hours total time. :-O
TheSQLGuru
President
Indicium Resources, Inc.
"Terri" <terri@.cybernets.com> wrote in message
news:f1vj1k$teb$1@.reader2.nmix.net...
> I'm looking for recommendations for 3rd party backup/restore software for
> SQL Server 2000.
> The software must be cluster aware. Ease and speed of recoverability are
> most important. I am not so concerned with compression ratio but rather
> the
> ease of which junior staff could restore databases at crunch time. Point
> in
> time restore is essential.
> thanks to any one who could offer an opinion.
>
3rd party backup/restore
I'm looking for recommendations for 3rd party backup/restore software for
SQL Server 2000.
The software must be cluster aware. Ease and speed of recoverability are
most important. I am not so concerned with compression ratio but rather the
ease of which junior staff could restore databases at crunch time. Point in
time restore is essential.
thanks to any one who could offer an opinion.A follow-up if I may. Do any of these products allow you to recovers users
at the server level when a restoring a database to a different server. It's
a hassle scripting and transferring logins.
"Terri" <terri@.cybernets.com> wrote in message
news:f1vj1k$teb$1@.reader2.nmix.net...
> I'm looking for recommendations for 3rd party backup/restore software for
> SQL Server 2000.
> The software must be cluster aware. Ease and speed of recoverability are
> most important. I am not so concerned with compression ratio but rather
the
> ease of which junior staff could restore databases at crunch time. Point
in
> time restore is essential.
> thanks to any one who could offer an opinion.
>|||"Terri" <terri@.cybernets.com> wrote in message
news:f1vj1k$teb$1@.reader2.nmix.net...
> I'm looking for recommendations for 3rd party backup/restore software for
> SQL Server 2000.
>
Any particular reason you can't use the built in backup tools for SQL Server
2000?
In any case, I'd recommend Litespeed for SQL Server.
> The software must be cluster aware. Ease and speed of recoverability are
> most important. I am not so concerned with compression ratio but rather
> the
> ease of which junior staff could restore databases at crunch time. Point
> in
> time restore is essential.
> thanks to any one who could offer an opinion.
>
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||I am very happy with the price, the speed, and the ease of restores and
backups using RED GATE. Instead of bak sizes of 80+ gig, they are about 10
gig. Its a great piece of software.
--
Regards,
Jamie
"Terri" wrote:
> A follow-up if I may. Do any of these products allow you to recovers users
> at the server level when a restoring a database to a different server. It's
> a hassle scripting and transferring logins.
>
> "Terri" <terri@.cybernets.com> wrote in message
> news:f1vj1k$teb$1@.reader2.nmix.net...
> > I'm looking for recommendations for 3rd party backup/restore software for
> > SQL Server 2000.
> >
> > The software must be cluster aware. Ease and speed of recoverability are
> > most important. I am not so concerned with compression ratio but rather
> the
> > ease of which junior staff could restore databases at crunch time. Point
> in
> > time restore is essential.
> >
> > thanks to any one who could offer an opinion.
> >
> >
>
>|||"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:OURUS2ykHHA.3484@.TK2MSFTNGP02.phx.gbl...
>
> "Terri" <terri@.cybernets.com> wrote in message
> news:f1vj1k$teb$1@.reader2.nmix.net...
> > I'm looking for recommendations for 3rd party backup/restore software
for
> > SQL Server 2000.
> >
> Any particular reason you can't use the built in backup tools for SQL
Server
> 2000?
I'm hoping it would be easier for an administrator to make a timely restore.
The performance boost can't hurt.
> In any case, I'd recommend Litespeed for SQL Server.
Thanks for your response, I'll take a look.|||"Terri" <terri@.cybernets.com> wrote in message
news:f2070q$2i9$1@.reader2.nmix.net...
> "Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in
> message
> news:OURUS2ykHHA.3484@.TK2MSFTNGP02.phx.gbl...
>>
>> "Terri" <terri@.cybernets.com> wrote in message
>> news:f1vj1k$teb$1@.reader2.nmix.net...
>> > I'm looking for recommendations for 3rd party backup/restore software
> for
>> > SQL Server 2000.
>> >
>> Any particular reason you can't use the built in backup tools for SQL
> Server
>> 2000?
> I'm hoping it would be easier for an administrator to make a timely
> restore.
> The performance boost can't hurt.
Easier?
Can't say I ever found
RESTORE DATABASE FOO from file="backup.bak" with NORECOVERY
all that complex :-)
But.. the performance boost is definitely a plus.
>> In any case, I'd recommend Litespeed for SQL Server.
> Thanks for your response, I'll take a look.
>|||Are Red Gate and Lightspeed cluster aware? Also, can those products restore
to a server on which the product does not reside?
Terri, if you REALLY want ease/speed of recoverability, get familiar with
the backupset system table and create a restore database script that takes a
parameter of @.DBName and creates all necessary RESTORE statements to
completely recover a database. Holy-Shit time is NOT the time to be
futzing with an interface you aren't familiar with. I used such a mechanism
(albeit a BIT more complex and hand-crafted at crunch time) earlier this
year to restore 719 databases having 6 backup files each to two different
servers in about 4 hours total time. :-O
--
TheSQLGuru
President
Indicium Resources, Inc.
"Terri" <terri@.cybernets.com> wrote in message
news:f1vj1k$teb$1@.reader2.nmix.net...
> I'm looking for recommendations for 3rd party backup/restore software for
> SQL Server 2000.
> The software must be cluster aware. Ease and speed of recoverability are
> most important. I am not so concerned with compression ratio but rather
> the
> ease of which junior staff could restore databases at crunch time. Point
> in
> time restore is essential.
> thanks to any one who could offer an opinion.
>
SQL Server 2000.
The software must be cluster aware. Ease and speed of recoverability are
most important. I am not so concerned with compression ratio but rather the
ease of which junior staff could restore databases at crunch time. Point in
time restore is essential.
thanks to any one who could offer an opinion.A follow-up if I may. Do any of these products allow you to recovers users
at the server level when a restoring a database to a different server. It's
a hassle scripting and transferring logins.
"Terri" <terri@.cybernets.com> wrote in message
news:f1vj1k$teb$1@.reader2.nmix.net...
> I'm looking for recommendations for 3rd party backup/restore software for
> SQL Server 2000.
> The software must be cluster aware. Ease and speed of recoverability are
> most important. I am not so concerned with compression ratio but rather
the
> ease of which junior staff could restore databases at crunch time. Point
in
> time restore is essential.
> thanks to any one who could offer an opinion.
>|||"Terri" <terri@.cybernets.com> wrote in message
news:f1vj1k$teb$1@.reader2.nmix.net...
> I'm looking for recommendations for 3rd party backup/restore software for
> SQL Server 2000.
>
Any particular reason you can't use the built in backup tools for SQL Server
2000?
In any case, I'd recommend Litespeed for SQL Server.
> The software must be cluster aware. Ease and speed of recoverability are
> most important. I am not so concerned with compression ratio but rather
> the
> ease of which junior staff could restore databases at crunch time. Point
> in
> time restore is essential.
> thanks to any one who could offer an opinion.
>
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||I am very happy with the price, the speed, and the ease of restores and
backups using RED GATE. Instead of bak sizes of 80+ gig, they are about 10
gig. Its a great piece of software.
--
Regards,
Jamie
"Terri" wrote:
> A follow-up if I may. Do any of these products allow you to recovers users
> at the server level when a restoring a database to a different server. It's
> a hassle scripting and transferring logins.
>
> "Terri" <terri@.cybernets.com> wrote in message
> news:f1vj1k$teb$1@.reader2.nmix.net...
> > I'm looking for recommendations for 3rd party backup/restore software for
> > SQL Server 2000.
> >
> > The software must be cluster aware. Ease and speed of recoverability are
> > most important. I am not so concerned with compression ratio but rather
> the
> > ease of which junior staff could restore databases at crunch time. Point
> in
> > time restore is essential.
> >
> > thanks to any one who could offer an opinion.
> >
> >
>
>|||"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:OURUS2ykHHA.3484@.TK2MSFTNGP02.phx.gbl...
>
> "Terri" <terri@.cybernets.com> wrote in message
> news:f1vj1k$teb$1@.reader2.nmix.net...
> > I'm looking for recommendations for 3rd party backup/restore software
for
> > SQL Server 2000.
> >
> Any particular reason you can't use the built in backup tools for SQL
Server
> 2000?
I'm hoping it would be easier for an administrator to make a timely restore.
The performance boost can't hurt.
> In any case, I'd recommend Litespeed for SQL Server.
Thanks for your response, I'll take a look.|||"Terri" <terri@.cybernets.com> wrote in message
news:f2070q$2i9$1@.reader2.nmix.net...
> "Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in
> message
> news:OURUS2ykHHA.3484@.TK2MSFTNGP02.phx.gbl...
>>
>> "Terri" <terri@.cybernets.com> wrote in message
>> news:f1vj1k$teb$1@.reader2.nmix.net...
>> > I'm looking for recommendations for 3rd party backup/restore software
> for
>> > SQL Server 2000.
>> >
>> Any particular reason you can't use the built in backup tools for SQL
> Server
>> 2000?
> I'm hoping it would be easier for an administrator to make a timely
> restore.
> The performance boost can't hurt.
Easier?
Can't say I ever found
RESTORE DATABASE FOO from file="backup.bak" with NORECOVERY
all that complex :-)
But.. the performance boost is definitely a plus.
>> In any case, I'd recommend Litespeed for SQL Server.
> Thanks for your response, I'll take a look.
>|||Are Red Gate and Lightspeed cluster aware? Also, can those products restore
to a server on which the product does not reside?
Terri, if you REALLY want ease/speed of recoverability, get familiar with
the backupset system table and create a restore database script that takes a
parameter of @.DBName and creates all necessary RESTORE statements to
completely recover a database. Holy-Shit time is NOT the time to be
futzing with an interface you aren't familiar with. I used such a mechanism
(albeit a BIT more complex and hand-crafted at crunch time) earlier this
year to restore 719 databases having 6 backup files each to two different
servers in about 4 hours total time. :-O
--
TheSQLGuru
President
Indicium Resources, Inc.
"Terri" <terri@.cybernets.com> wrote in message
news:f1vj1k$teb$1@.reader2.nmix.net...
> I'm looking for recommendations for 3rd party backup/restore software for
> SQL Server 2000.
> The software must be cluster aware. Ease and speed of recoverability are
> most important. I am not so concerned with compression ratio but rather
> the
> ease of which junior staff could restore databases at crunch time. Point
> in
> time restore is essential.
> thanks to any one who could offer an opinion.
>
Subscribe to:
Posts (Atom)