Restore db to another server

I'm in the process of migrating db:s from SQL 2000 (SP2) on Windows 2000
(SP4) to SQL 2000 (SP4) on Windows Server 2003 (SP1).
I'm restoring db from tape w. BackupExec 9.0. The first time I did a restore
it was cancelled after 10% write; error 34113 on BackupExec server, and
repeated error 57859 on destination SQL server.
When rerun job, no data is written and job cancels with same error in
BackupExec server, and new error in destination SQL server: 57859 --
"Exclusive access couldn not be obtained because the database is in use." (It
seems to me it's not in use, nobody uses this server yet.)
Strange thing is, I can restore another (test) database from same tape
without any problems.
Happy to get any hints or guidelines, I'm kinda stuck.
I deleted the restored database on new SQL server an reran the restore job,
and everything worked OK -- and so I will never know what went wrong the
first time, but will nevertheless be able to spend the weekend with family
instead of SQL.
Thanks for taking time, if you took any.
"JSL" wrote:

> I'm in the process of migrating db:s from SQL 2000 (SP2) on Windows 2000
> (SP4) to SQL 2000 (SP4) on Windows Server 2003 (SP1).
> I'm restoring db from tape w. BackupExec 9.0. The first time I did a restore
> it was cancelled after 10% write; error 34113 on BackupExec server, and
> repeated error 57859 on destination SQL server.
> When rerun job, no data is written and job cancels with same error in
> BackupExec server, and new error in destination SQL server: 57859 --
> "Exclusive access couldn not be obtained because the database is in use." (It
> seems to me it's not in use, nobody uses this server yet.)
> Strange thing is, I can restore another (test) database from same tape
> without any problems.
> Happy to get any hints or guidelines, I'm kinda stuck.
|||Next time, use sp_who to see who is using the database.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JSL" <JSL@.discussions.microsoft.com> wrote in message
news:90762CE8-604D-4BD5-A1DE-9645952022C9@.microsoft.com...[vbcol=seagreen]
>I deleted the restored database on new SQL server an reran the restore job,
> and everything worked OK -- and so I will never know what went wrong the
> first time, but will nevertheless be able to spend the weekend with family
> instead of SQL.
> Thanks for taking time, if you took any.
> "JSL" wrote:

Restore db to another server

I'm in the process of migrating db:s from SQL 2000 (SP2) on Windows 2000
(SP4) to SQL 2000 (SP4) on Windows Server 2003 (SP1).
I'm restoring db from tape w. BackupExec 9.0. The first time I did a restore
it was cancelled after 10% write; error 34113 on BackupExec server, and
repeated error 57859 on destination SQL server.
When rerun job, no data is written and job cancels with same error in
BackupExec server, and new error in destination SQL server: 57859 --
"Exclusive access couldn not be obtained because the database is in use." (It
seems to me it's not in use, nobody uses this server yet.)
Strange thing is, I can restore another (test) database from same tape
without any problems.
Happy to get any hints or guidelines, I'm kinda stuck.I deleted the restored database on new SQL server an reran the restore job,
and everything worked OK -- and so I will never know what went wrong the
first time, but will nevertheless be able to spend the weekend with family
instead of SQL.
Thanks for taking time, if you took any.
"JSL" wrote:
> I'm in the process of migrating db:s from SQL 2000 (SP2) on Windows 2000
> (SP4) to SQL 2000 (SP4) on Windows Server 2003 (SP1).
> I'm restoring db from tape w. BackupExec 9.0. The first time I did a restore
> it was cancelled after 10% write; error 34113 on BackupExec server, and
> repeated error 57859 on destination SQL server.
> When rerun job, no data is written and job cancels with same error in
> BackupExec server, and new error in destination SQL server: 57859 --
> "Exclusive access couldn not be obtained because the database is in use." (It
> seems to me it's not in use, nobody uses this server yet.)
> Strange thing is, I can restore another (test) database from same tape
> without any problems.
> Happy to get any hints or guidelines, I'm kinda stuck.|||Next time, use sp_who to see who is using the database.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JSL" <JSL@.discussions.microsoft.com> wrote in message
news:90762CE8-604D-4BD5-A1DE-9645952022C9@.microsoft.com...
>I deleted the restored database on new SQL server an reran the restore job,
> and everything worked OK -- and so I will never know what went wrong the
> first time, but will nevertheless be able to spend the weekend with family
> instead of SQL.
> Thanks for taking time, if you took any.
> "JSL" wrote:
>> I'm in the process of migrating db:s from SQL 2000 (SP2) on Windows 2000
>> (SP4) to SQL 2000 (SP4) on Windows Server 2003 (SP1).
>> I'm restoring db from tape w. BackupExec 9.0. The first time I did a restore
>> it was cancelled after 10% write; error 34113 on BackupExec server, and
>> repeated error 57859 on destination SQL server.
>> When rerun job, no data is written and job cancels with same error in
>> BackupExec server, and new error in destination SQL server: 57859 --
>> "Exclusive access couldn not be obtained because the database is in use." (It
>> seems to me it's not in use, nobody uses this server yet.)
>> Strange thing is, I can restore another (test) database from same tape
>> without any problems.
>> Happy to get any hints or guidelines, I'm kinda stuck.

Restore db to another server

I'm in the process of migrating db:s from SQL 2000 (SP2) on Windows 2000
(SP4) to SQL 2000 (SP4) on Windows Server 2003 (SP1).
I'm restoring db from tape w. BackupExec 9.0. The first time I did a restore
it was cancelled after 10% write; error 34113 on BackupExec server, and
repeated error 57859 on destination SQL server.
When rerun job, no data is written and job cancels with same error in
BackupExec server, and new error in destination SQL server: 57859 --
"Exclusive access couldn not be obtained because the database is in use." (I
t
seems to me it's not in use, nobody uses this server yet.)
Strange thing is, I can restore another (test) database from same tape
without any problems.
Happy to get any hints or guidelines, I'm kinda stuck.I deleted the restored database on new SQL server an reran the restore job,
and everything worked OK -- and so I will never know what went wrong the
first time, but will nevertheless be able to spend the weekend with family
instead of SQL.
Thanks for taking time, if you took any.
"JSL" wrote:

> I'm in the process of migrating db:s from SQL 2000 (SP2) on Windows 2000
> (SP4) to SQL 2000 (SP4) on Windows Server 2003 (SP1).
> I'm restoring db from tape w. BackupExec 9.0. The first time I did a resto
re
> it was cancelled after 10% write; error 34113 on BackupExec server, and
> repeated error 57859 on destination SQL server.
> When rerun job, no data is written and job cancels with same error in
> BackupExec server, and new error in destination SQL server: 57859 --
> "Exclusive access couldn not be obtained because the database is in use."
(It
> seems to me it's not in use, nobody uses this server yet.)
> Strange thing is, I can restore another (test) database from same tape
> without any problems.
> Happy to get any hints or guidelines, I'm kinda stuck.|||Next time, use sp_who to see who is using the database.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JSL" <JSL@.discussions.microsoft.com> wrote in message
news:90762CE8-604D-4BD5-A1DE-9645952022C9@.microsoft.com...[vbcol=seagreen]
>I deleted the restored database on new SQL server an reran the restore job,
> and everything worked OK -- and so I will never know what went wrong the
> first time, but will nevertheless be able to spend the weekend with family
> instead of SQL.
> Thanks for taking time, if you took any.
> "JSL" wrote:
>sql

restore database on SQL Server 6.5

Hi,
I restore a database using a 3rd party software. The
restore job was cancelled but the process "loading
database" is still in the output of "sp_who". I could not
kill it. Do I have to reboot the server to get rid of it
or I can start a job to continue to restore this database?
Thanks for help,
Hi,
Try STOP and START the MSSQL Server service. After that start the Loading of
database again from ISQL_W.
LOAD database <dbname> from disk='c:\backup\dbname.DMP' with stats=10
Note: stats=10 will show the percentage of load completed.
Thanks
Hari
MCDBA
"Julia" <anonymous@.discussions.microsoft.com> wrote in message
news:1d83601c453e7$425a6e30$a401280a@.phx.gbl...
> Hi,
> I restore a database using a 3rd party software. The
> restore job was cancelled but the process "loading
> database" is still in the output of "sp_who". I could not
> kill it. Do I have to reboot the server to get rid of it
> or I can start a job to continue to restore this database?
> Thanks for help,

restore database on SQL Server 6.5

Hi,
I restore a database using a 3rd party software. The
restore job was cancelled but the process "loading
database" is still in the output of "sp_who". I could not
kill it. Do I have to reboot the server to get rid of it
or I can start a job to continue to restore this database?
Thanks for help,Hi,
Try STOP and START the MSSQL Server service. After that start the Loading of
database again from ISQL_W.
LOAD database <dbname> from disk='c:\backup\dbname.DMP' with stats=10
Note: stats=10 will show the percentage of load completed.
Thanks
Hari
MCDBA
"Julia" <anonymous@.discussions.microsoft.com> wrote in message
news:1d83601c453e7$425a6e30$a401280a@.phx
.gbl...
> Hi,
> I restore a database using a 3rd party software. The
> restore job was cancelled but the process "loading
> database" is still in the output of "sp_who". I could not
> kill it. Do I have to reboot the server to get rid of it
> or I can start a job to continue to restore this database?
> Thanks for help,sql

restore database on SQL Server 6.5

Hi,
I restore a database using a 3rd party software. The
restore job was cancelled but the process "loading
database" is still in the output of "sp_who". I could not
kill it. Do I have to reboot the server to get rid of it
or I can start a job to continue to restore this database?
Thanks for help,Hi,
Try STOP and START the MSSQL Server service. After that start the Loading of
database again from ISQL_W.
LOAD database <dbname> from disk='c:\backup\dbname.DMP' with stats=10
Note: stats=10 will show the percentage of load completed.
Thanks
Hari
MCDBA
"Julia" <anonymous@.discussions.microsoft.com> wrote in message
news:1d83601c453e7$425a6e30$a401280a@.phx.gbl...
> Hi,
> I restore a database using a 3rd party software. The
> restore job was cancelled but the process "loading
> database" is still in the output of "sp_who". I could not
> kill it. Do I have to reboot the server to get rid of it
> or I can start a job to continue to restore this database?
> Thanks for help,

Restore Database action not responding

I followed the "Restore Database to a new Server" process using Enterprise
Manager and T-SQL using the WITH MOVE option. Both processes seem to be
hanging.
In EM, the Restore Progress bar shows it is restoring but no progress is made.
In T-SQL, I just receive Executing Query Batch...
Any ideas on what is going on? What do I need to look at?
Thanks-
Deb
Deb
RESTORE may need to create the database before the restore actually begins
and this can take considerable time. Is this a large database?
Hope this helps.
Dan Guzman
SQL Server MVP
"Deb" <Deb@.discussions.microsoft.com> wrote in message
news:30CD3ECC-B47B-44EB-A396-F3DA717F1FB2@.microsoft.com...
>I followed the "Restore Database to a new Server" process using Enterprise
> Manager and T-SQL using the WITH MOVE option. Both processes seem to be
> hanging.
> In EM, the Restore Progress bar shows it is restoring but no progress is
> made.
> In T-SQL, I just receive Executing Query Batch...
> Any ideas on what is going on? What do I need to look at?
> Thanks-
> Deb
>
> --
> Deb
|||Ahhh. I will let it run overnight then. It is almost 14GB.
Deb
"Dan Guzman" wrote:

> RESTORE may need to create the database before the restore actually begins
> and this can take considerable time. Is this a large database?
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Deb" <Deb@.discussions.microsoft.com> wrote in message
> news:30CD3ECC-B47B-44EB-A396-F3DA717F1FB2@.microsoft.com...
>
>
|||I wouldn't expect this to take more than a few hours, even on modest
hardware. You can get an idea of how long it might take by checking out the
performance monitor metric: physical disk/bytes per sec.
Hope this helps.
Dan Guzman
SQL Server MVP
"Deb" <Deb@.discussions.microsoft.com> wrote in message
news:A980EE61-E755-4837-90CE-728E794809C5@.microsoft.com...[vbcol=seagreen]
> Ahhh. I will let it run overnight then. It is almost 14GB.
> --
> Deb
>
> "Dan Guzman" wrote:

Restore Database action not responding

I followed the "Restore Database to a new Server" process using Enterprise
Manager and T-SQL using the WITH MOVE option. Both processes seem to be
hanging.
In EM, the Restore Progress bar shows it is restoring but no progress is mad
e.
In T-SQL, I just receive Executing Query Batch...
Any ideas on what is going on? What do I need to look at?
Thanks-
Deb
DebRESTORE may need to create the database before the restore actually begins
and this can take considerable time. Is this a large database?
Hope this helps.
Dan Guzman
SQL Server MVP
"Deb" <Deb@.discussions.microsoft.com> wrote in message
news:30CD3ECC-B47B-44EB-A396-F3DA717F1FB2@.microsoft.com...
>I followed the "Restore Database to a new Server" process using Enterprise
> Manager and T-SQL using the WITH MOVE option. Both processes seem to be
> hanging.
> In EM, the Restore Progress bar shows it is restoring but no progress is
> made.
> In T-SQL, I just receive Executing Query Batch...
> Any ideas on what is going on? What do I need to look at?
> Thanks-
> Deb
>
> --
> Deb|||Ahhh. I will let it run overnight then. It is almost 14GB.
--
Deb
"Dan Guzman" wrote:

> RESTORE may need to create the database before the restore actually begins
> and this can take considerable time. Is this a large database?
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Deb" <Deb@.discussions.microsoft.com> wrote in message
> news:30CD3ECC-B47B-44EB-A396-F3DA717F1FB2@.microsoft.com...
>
>|||I wouldn't expect this to take more than a few hours, even on modest
hardware. You can get an idea of how long it might take by checking out the
performance monitor metric: physical disk/bytes per sec.
Hope this helps.
Dan Guzman
SQL Server MVP
"Deb" <Deb@.discussions.microsoft.com> wrote in message
news:A980EE61-E755-4837-90CE-728E794809C5@.microsoft.com...[vbcol=seagreen]
> Ahhh. I will let it run overnight then. It is almost 14GB.
> --
> Deb
>
> "Dan Guzman" wrote:
>

Restore Database action not responding

I followed the "Restore Database to a new Server" process using Enterprise
Manager and T-SQL using the WITH MOVE option. Both processes seem to be
hanging.
In EM, the Restore Progress bar shows it is restoring but no progress is made.
In T-SQL, I just receive Executing Query Batch...
Any ideas on what is going on? What do I need to look at?
Thanks-
Deb
--
DebRESTORE may need to create the database before the restore actually begins
and this can take considerable time. Is this a large database?
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Deb" <Deb@.discussions.microsoft.com> wrote in message
news:30CD3ECC-B47B-44EB-A396-F3DA717F1FB2@.microsoft.com...
>I followed the "Restore Database to a new Server" process using Enterprise
> Manager and T-SQL using the WITH MOVE option. Both processes seem to be
> hanging.
> In EM, the Restore Progress bar shows it is restoring but no progress is
> made.
> In T-SQL, I just receive Executing Query Batch...
> Any ideas on what is going on? What do I need to look at?
> Thanks-
> Deb
>
> --
> Deb|||Ahhh. I will let it run overnight then. It is almost 14GB.
--
Deb
"Dan Guzman" wrote:
> RESTORE may need to create the database before the restore actually begins
> and this can take considerable time. Is this a large database?
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Deb" <Deb@.discussions.microsoft.com> wrote in message
> news:30CD3ECC-B47B-44EB-A396-F3DA717F1FB2@.microsoft.com...
> >I followed the "Restore Database to a new Server" process using Enterprise
> > Manager and T-SQL using the WITH MOVE option. Both processes seem to be
> > hanging.
> >
> > In EM, the Restore Progress bar shows it is restoring but no progress is
> > made.
> >
> > In T-SQL, I just receive Executing Query Batch...
> >
> > Any ideas on what is going on? What do I need to look at?
> >
> > Thanks-
> > Deb
> >
> >
> >
> > --
> > Deb
>
>|||I wouldn't expect this to take more than a few hours, even on modest
hardware. You can get an idea of how long it might take by checking out the
performance monitor metric: physical disk/bytes per sec.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Deb" <Deb@.discussions.microsoft.com> wrote in message
news:A980EE61-E755-4837-90CE-728E794809C5@.microsoft.com...
> Ahhh. I will let it run overnight then. It is almost 14GB.
> --
> Deb
>
> "Dan Guzman" wrote:
>> RESTORE may need to create the database before the restore actually
>> begins
>> and this can take considerable time. Is this a large database?
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Deb" <Deb@.discussions.microsoft.com> wrote in message
>> news:30CD3ECC-B47B-44EB-A396-F3DA717F1FB2@.microsoft.com...
>> >I followed the "Restore Database to a new Server" process using
>> >Enterprise
>> > Manager and T-SQL using the WITH MOVE option. Both processes seem to
>> > be
>> > hanging.
>> >
>> > In EM, the Restore Progress bar shows it is restoring but no progress
>> > is
>> > made.
>> >
>> > In T-SQL, I just receive Executing Query Batch...
>> >
>> > Any ideas on what is going on? What do I need to look at?
>> >
>> > Thanks-
>> > Deb
>> >
>> >
>> >
>> > --
>> > Deb
>>

restore could not start database

Hi,

I am trying to restore SQL2K DB backup to SQL2005 Express. The process goes fine, but at the end of the process (100% progress), it shows error Restore Could not start database.

It does not provide more detail to remedy the error.

Anybody faced this problem and have any solution?

Thanks,

Hiten

What happens when you manually start the sql server services?|||

SQL server services are running, but the database is not online. It puts the database in to suspect state.

I looked in to event logs, and it turned out that the database I was restoring already had 'sys' sql user , since in 2005 sys user is reserved, the restore operation tried to rename it to something else, the log shows following message

Warning: User "sys" (principal_id = 24) in database "Test" has been renamed to "_ID_0x00000018_RENAMED_FROM_sys". "sys" is a reserved user or schema name in this version of SQL Server.

There were few other error/warnings for objects used by sys.

Warning: A column nullability inconsistency was detected in the metadata of index "_WA_Sys_CurrentStatusID_7080FE81" (index_id = 2) on object ID 1887501953 in database "Test". 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_NextStatusID_7080FE81" (index_id = 3) on object ID 1887501953 in database "Test". 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_TransitionString_7080FE81" (index_id = 4) on object ID 1887501953 in database "Test". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.

and at last

Warning: Database "Test" was marked suspect because of actions taken during upgrade. See errorlog or eventlog for more information. Use ALTER DATABASE to bring the database online. The database will come online in restricted_user state.

RESTORE could not start database 'Test'.

The database 'Test' is marked RESTORING and is in a state that does not allow recovery to be run.

In the end, it puts database to suspect. I don't know how to bring it back to online for multiple users. When I tried to bring it online using ALTER DATABASE command, it brought it online for single user only, which did not serve my purpose, and I don't know what needs to be cleaned up to this database.

I hope this will give u some idea of what happened.

I would appreciate any suggestion..

Thanks,

Hiten