Unable to restore DB on Mapped Network Drive

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

New to SQL Server Programming

Unable to restore DB on Mapped Network Drive

Author

Topic

manojkumarmajhi
Starting Member

1 Post

Posted - 2010-12-16 : 22:44:18

Hi There,

I have my SQL Server2005 in CLUSTER Based environment & I have a Mapped Network Drive, I need to restore the DB and needs to put the .ldf & .mdf files into the mapped Drive. After giving the UNC Path on the restore as location giving error " \\sharename\*.MDF is on a network taht is not supported for database files.

I need all of your support........

Manoj Kumar Majhi
N/W Admin

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-12-16 : 23:19:37

You can not restore the database files onto a mapped network. It is not possible.

You can have your backup file there, but you can't place your database files there.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2010-12-17 : 09:50:33

SQL has a number of requirements for its data location and network drives don't support them. The data and log files must be on a local drive, SAN drive or iSCSI drive.

--
Gail Shaw
SQL Server MVP

russell
Pyro-ma-ni-yak

5072 Posts

Posted - 2010-12-17 : 10:09:49

It is generally sound advice not to use network storage, but it is in fact allowed.

Trace flag 1807 bypasses the check. There are several issues with doing this, and it is generally a bad idea, but in some rare cases it makes sense to do so.

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2010-12-17 : 12:40:45

It can be allowed. It's not by default and it's strongly not recommended. That traceflag bypasses all the IO requirement checks. If you use that and there are any network glitches, your DB will be corrupt or suspect afterwards.

--
Gail Shaw
SQL Server MVP

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-12-17 : 13:17:01

Oh my gosh, I can't believe MS would allow it via a trace flag. Network glitches are bound to happen.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

russell
Pyro-ma-ni-yak

5072 Posts

Posted - 2010-12-17 : 13:23:32

As I said, I agree that it's a bad practice, but I have seen it done. It was for non-critical archived data where a NAS was used for the backend (for that db only).

I suppose I only responded for the sake of completeness. Wasn't trying to be argumentative

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-12-17 : 13:37:30

I could see the reason to use it for a NAS, but not for just a mapped network drive of some other server that has disk space.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

russell
Pyro-ma-ni-yak

5072 Posts

Posted - 2010-12-17 : 13:50:00

Agreed

robvolk
Most Valuable Yak

15732 Posts

Posted - 2010-12-17 : 13:53:35

quote:
Oh my gosh, I can't believe MS would allow it via a trace flag. Network glitches are bound to happen.

So we probably shouldn't tell you that it's available without a trace flag in R2?

http://blogs.msdn.com/b/sqlserverfaq/archive/2010/05/13/inf-new-sql-server-features-in-sql-server-2008-r2-part-1.aspx

russell
Pyro-ma-ni-yak

5072 Posts

Posted - 2010-12-17 : 13:55:22

They might as well bring back nolog/truncate_only too lol