Database files on a shared folder

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

SQL Server 2005 Forums

Express Edition and Compact Edition (2005)

Database files on a shared folder

Author

Topic

HCLollo
Starting Member

49 Posts

Posted - 2009-06-24 : 09:07:39

Good afternoon to everyone!

It's unfortunately been a while since I last put my hands on a SQL
Server installation (long work detours) but now I have to tinker with
a SSEE installation, as I will describe.

A software tool installed with one of the devices I work with, uses
a SSEE instance, which installs and configures all by itself; until
here, everything is going fine...problem is, the application is a
medical one, and now that policies are going to verge on the safer
side, customers (tipically IT managers at Hospital's site) want the
application to write data onto backup-able folders...which are on
a network drive.

Now, I gather that this goes directly towards data-unsecureness, so
it should be impossible, but does any of the Almighty Gurus on this
forum know if it's possible to set the DB data and log files to
"\\whatever\alright\data.mdf" and "\\whatever\alright\data_log.ldf"?

If not, are there some ways to serially export the data onto a shared
folder? I can't rely on the user doing the manual backup, so I was
thinking about a simple trigger, though I fear I will have to specify
manually all the data (which will obviously result in a great mess

).

...sob...I feel knowledge leaking from my mind...

Thank you in advance!

HCL

"If it works fine, then it doesn't have enough features"

dinakar
Master Smack Fu Yak Hacker

2507 Posts

Posted - 2009-06-24 : 09:58:00

ofcourse... create a mount point and point your data and log fils there.. you could also move your existing files to the network drive by using the ALTER DATABASE option.. check out books online.. they have some sample code too..

Dinakar Nethi
************************
Life is short. Enjoy it.
************************
http://weblogs.sqlteam.com/dinakar/

HCLollo
Starting Member

49 Posts

Posted - 2009-06-29 : 08:20:23

Hmm...

"The path specified by "X:\Database\filename.mdf" is not in a valid directory."

where X: is a mounted network share...

I still have some doubts about the actual possibility of setting a
primary data on a mounted drive...though it could also be due to
user settings...

HCL

"If it works fine, then it doesn't have enough features"

ScottWhigham
Starting Member

49 Posts

Posted - 2009-09-03 : 06:33:11

quote:
Originally posted by dinakar

ofcourse... create a mount point and point your data and log fils there.. you could also move your existing files to the network drive by using the ALTER DATABASE option.. check out books online.. they have some sample code too..

I'm not sure where you got this information, dinakar. BOL specifically states: "The file must reside on one of the following devices: the local server on which SQL Server is installed, a Storage Area Network [SAN], or an iSCSI-based network." You are not allowed to use CREATE DATABASE with mapped drives or shared folders - you get an error:

Msg 5110, Level 16, State 2, Line 1
The file "\\whatever\alright\data.mdf" is on a network path that is not supported for database files.

========================================================

I have about 1,000 video tutorials on SQL Server 2008, 2005, and 2000 over at http://www.learnitfirst.com/Database-Professionals.aspx

ScottWhigham
Starting Member

49 Posts

Posted - 2009-09-03 : 06:36:21

quote:
Originally posted by HCLollo

...want the
application to write data onto backup-able folders...which are on
a network drive.

If not, are there some ways to serially export the data onto a shared
folder?[B)

I know this is an older post (2 months) but I just wanted to reply to make sure other newbies coming through this don't get confused.

1) As stated above, you cannot place database files on network shares or mapped drives

2) The proper approach here is to create either a SQL Server job to perform your backups or to create a maintenance plan to perform your backups. Since you mention you haven't spent too much time with SQL Server, I'd opt for a maintenance plan. Just make sure the SQL Agent service is always running - it's what kicks off any jobs or scheduled activities in SQL Server.

========================================================

I have about 1,000 video tutorials on SQL Server 2008, 2005, and 2000 over at http://www.learnitfirst.com/Database-Professionals.aspx

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources