Database restore problem

A customer's Windows 2000 server would not reboot. They
ran a repair, but the drive letters on the server moved
ahead two spots. The drive letter D is now drive F.
I attempted a restore of a database through Enterprise
Manager, but I get the following error message :
"Device activation error: the physical file name d:\sql
db\otg.mdf: may be incorrect. File 'otg data' cannot be
restored to d:\sql db\otg.mdf'. Use with move to identify
a valid location for the file. Device activation error.
The physical file name 'D:\sql db\otglog.ldf may be
incorrect. File 'otglog' cannot be restored to 'd:\sql
db\otglog.ldf.' Use with move to identify a valid location
for the file. Restore db is terminating abnormally."
The original database files were located on C. A backup of
the database was saved to D.
What can I do to restore this database? Can anyone suggest
a query that restores the database to its previous state?
Thanks for your help.Hello Craig !
If you restore in EM you should change the path where you want to place the
new datafiles from the backup.
Please note, that the directories will NOT be created by EM, they must be
created before restoring the database.
HTH, Jens Süßmeyer.|||Try this:
RESTORE DATABASE otg
FROM DISK= 'c:\wherever the .bak file is'
WITH RECOVERY,replace,
MOVE 'otg_data' TO 'd:\sql_db\otg.mdf',
MOVE 'otgLog' TO 'd:\sql_db\otglog.ldf.'
Make sure you have enough permissions, with OTG imaging database you can use
the sysop user ;)
HTH
--
Ray Higdon MCSE, MCDBA, CCNA
--
"Craig Kornacki" <ckornack@.localnet.com> wrote in message
news:034701c36f5b$2e13c320$a301280a@.phx.gbl...
> A customer's Windows 2000 server would not reboot. They
> ran a repair, but the drive letters on the server moved
> ahead two spots. The drive letter D is now drive F.
> I attempted a restore of a database through Enterprise
> Manager, but I get the following error message :
> "Device activation error: the physical file name d:\sql
> db\otg.mdf: may be incorrect. File 'otg data' cannot be
> restored to d:\sql db\otg.mdf'. Use with move to identify
> a valid location for the file. Device activation error.
> The physical file name 'D:\sql db\otglog.ldf may be
> incorrect. File 'otglog' cannot be restored to 'd:\sql
> db\otglog.ldf.' Use with move to identify a valid location
> for the file. Restore db is terminating abnormally."
> The original database files were located on C. A backup of
> the database was saved to D.
> What can I do to restore this database? Can anyone suggest
> a query that restores the database to its previous state?
> Thanks for your help.|||I know it's late, but what I would do is change the Drive letter to the
original drive letter using windows disk manager... This will likely prevent
other mapping kinds of errors from other applications as well.
"Craig Kornacki" <ckornack@.localnet.com> wrote in message
news:034701c36f5b$2e13c320$a301280a@.phx.gbl...
> A customer's Windows 2000 server would not reboot. They
> ran a repair, but the drive letters on the server moved
> ahead two spots. The drive letter D is now drive F.
> I attempted a restore of a database through Enterprise
> Manager, but I get the following error message :
> "Device activation error: the physical file name d:\sql
> db\otg.mdf: may be incorrect. File 'otg data' cannot be
> restored to d:\sql db\otg.mdf'. Use with move to identify
> a valid location for the file. Device activation error.
> The physical file name 'D:\sql db\otglog.ldf may be
> incorrect. File 'otglog' cannot be restored to 'd:\sql
> db\otglog.ldf.' Use with move to identify a valid location
> for the file. Restore db is terminating abnormally."
> The original database files were located on C. A backup of
> the database was saved to D.
> What can I do to restore this database? Can anyone suggest
> a query that restores the database to its previous state?
> Thanks for your help.|||Will this query work even if there is no D drive on the
server?
>--Original Message--
>Try this:
>RESTORE DATABASE otg
>FROM DISK= 'c:\wherever the .bak file is'
> WITH RECOVERY,replace,
> MOVE 'otg_data' TO 'd:\sql_db\otg.mdf',
> MOVE 'otgLog' TO 'd:\sql_db\otglog.ldf.'
>Make sure you have enough permissions, with OTG imaging
database you can use
>the sysop user ;)
>HTH
>--
>Ray Higdon MCSE, MCDBA, CCNA
>--
>"Craig Kornacki" <ckornack@.localnet.com> wrote in message
>news:034701c36f5b$2e13c320$a301280a@.phx.gbl...
>> A customer's Windows 2000 server would not reboot.
They
>> ran a repair, but the drive letters on the server moved
>> ahead two spots. The drive letter D is now drive F.
>> I attempted a restore of a database through Enterprise
>> Manager, but I get the following error message :
>> "Device activation error: the physical file name
d:\sql
>> db\otg.mdf: may be incorrect. File 'otg data' cannot
be
>> restored to d:\sql db\otg.mdf'. Use with move to
identify
>> a valid location for the file. Device activation
error.
>> The physical file name 'D:\sql db\otglog.ldf may be
>> incorrect. File 'otglog' cannot be restored to 'd:\sql
>> db\otglog.ldf.' Use with move to identify a valid
location
>> for the file. Restore db is terminating abnormally."
>> The original database files were located on C. A
backup of
>> the database was saved to D.
>> What can I do to restore this database? Can anyone
suggest
>> a query that restores the database to its previous
state?
>> Thanks for your help.
>
>.
>

Database Restore caused production server reboot

I got a production server with the following hard ware software
Server: Dell PowerEdge 2950
Storage: FS SAN 650
Memory: 4GB
windows 2003 standard (sp1)
sql server 2005 standard (9.00.2153)
There are five user databases, their size range varies from 12GB to 15 GB
I wanted archived data from one of the databases, so started database
restore process from old backups that made server to freeze then rebooted it
automatically. I found the following messages in the event log. My question
is how a restore process will bring server shutdown. With the same memory
and i had 150 databases in dev environment and never got a server reboot
with database restore. Can you please let me know your expert ideas what
else might have caused the reboot if not the restore process.
Date 2/19/2008 11:15:48 AM
Log Windows NT (Application)
Source MSSQL$xxx
Category Logon
Event 3221242661
Computer xxxxxx
Message
SQL Server failed with error code 0xc0000000 to spawn a thread to process a
new login or connection. Check the SQL Server error log and the Windows
event logs for information about possible related problems. [CLIENT:
111.111.11.164]
Date 2/19/2008 11:22:09 AM
Log Windows NT (Application)
Source MSSQL$xxxxx
Category Logon
Event 3221242666
Computer xxxxxxx
Message
The server was unable to load the SSL provider library needed to log in; the
connection has been closed. SSL is used to encrypt either the login sequence
or all communications, depending on how the administrator has configured the
server. See Books Online for information on this error message: 0x2746.
[CLIENT: 111.111.111.5]
-- --
Thanks,
Subbu
Hi
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1308037&SiteID=1
http://www.sqlservermart.com/resources/SynAttackProtect.aspx
"Subbu" <subbudamireddy@.hotmail.com> wrote in message
news:%23g0IhlWdIHA.3400@.TK2MSFTNGP03.phx.gbl...
>I got a production server with the following hard ware software
> Server: Dell PowerEdge 2950
> Storage: FS SAN 650
> Memory: 4GB
> windows 2003 standard (sp1)
> sql server 2005 standard (9.00.2153)
> There are five user databases, their size range varies from 12GB to 15 GB
> I wanted archived data from one of the databases, so started database
> restore process from old backups that made server to freeze then rebooted
> it automatically. I found the following messages in the event log. My
> question is how a restore process will bring server shutdown. With the
> same memory and i had 150 databases in dev environment and never got a
> server reboot with database restore. Can you please let me know your
> expert ideas what else might have caused the reboot if not the restore
> process.
> Date 2/19/2008 11:15:48 AM
> Log Windows NT (Application)
> Source MSSQL$xxx
> Category Logon
> Event 3221242661
> Computer xxxxxx
> Message
> SQL Server failed with error code 0xc0000000 to spawn a thread to process
> a new login or connection. Check the SQL Server error log and the Windows
> event logs for information about possible related problems. [CLIENT:
> 111.111.11.164]
>
> ----
> Date 2/19/2008 11:22:09 AM
> Log Windows NT (Application)
> Source MSSQL$xxxxx
> Category Logon
> Event 3221242666
> Computer xxxxxxx
> Message
> The server was unable to load the SSL provider library needed to log in;
> the connection has been closed. SSL is used to encrypt either the login
> sequence or all communications, depending on how the administrator has
> configured the server. See Books Online for information on this error
> message: 0x2746. [CLIENT: 111.111.111.5]
> -- --
> Thanks,
> Subbu
>
>
>