 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / General / Security / August 2006SQL Server Can Not See Shared Drive
It all stared by observing and error when running Bulk Insert with a sp where the input file was on the C drive – it was fine. Then I switched to where the file was on a shared network drive – it failed with Access Denied. I did a work around which works fine but did not still resolve the Access Denied issue. I then started thinking about the SQL security. I was wondering if SQL itself could see a shared drive. For example, making a Device to a different drive or even setting up the MDF/LDF to a new database to a different drive. My test proved that it failed on all counts. It could only see the C drive. After my research, I discovered first that SQL was starting under Local System account. I changed that to a domain account that has absolutely full System Administrator writes and can see everything on our environment. I then tried making a new database and putting the MDF/LDF to a mapped shared drive. It could not see the shared drive – period. I am running Windows Server 2003 and SQL Server 2000. The domain account I am using to start SQL Server has full rights and can see the environment. Before I have to open the checkbook and call MS to open a ticket, do you have any suggestions? MG Mapped drives are profile dependent. And they are not all that reliable with services due to them being profile based. You always want to use UNC paths instead of mapped drives. The references to network locations should be in the form of: \\ServerName\ShareName If you are accessing network resources, you need to be using a domain account for the SQL service account. -Sue >It all stared by observing and error when running Bulk Insert with a sp where >the input file was on the C drive it was fine. Then I switched to where the [quoted text clipped - 20 lines] > >MG Sue, Thanks but that is pretty much what I am doing. SQL is starting under a domain account. That account has full priviledges and rights accross the entire network. To help you understand what I am seeing, here is an example. If I decide to creat a new database and select Database and right click New Database. The enter a name, (i.e. TestToday) and go to the Database file tab. Then select Location to put the MDF in a shared drive, there is nothing that appears in the window except the C drive. I am expecting to be able to put the MDF on another location at that point. I am expecting to see the other mapped drives that the domain account I am using can see. The domain account can see the drive I want to put the MDF on but SQL can not and sql is running under that SAME domain account. Let me know if you have any other ideas. Thanks, MG > Mapped drives are profile dependent. And they are not all > that reliable with services due to them being profile based. [quoted text clipped - 31 lines] > > > >MG I'm not sure that is really what you are doing. You keep referring to mapped drives. You should not be using mapped drives. You should be using UNC paths. I'm not sure what you mean by a shared drive - a share or a mapped drive or a UNC path to a share? Are you expecting to see non-local drives from another server show up as drive letters? That is a mapped drive (typically - SAN volumes will be seen as a drive letter), not a UNC path. When you say you are expecting to "see" mapped drives, that kind of sounds like you are not using UNC paths. Also, putting the data files on network drives like this isn't recommended. You need to place them on local drives (or DAS) or on SAN volumes which would appear as local drives. Refer to the following article: Description of support for network database files in SQL Server http://support.microsoft.com/?id=304261 -Sue >Sue, >Thanks but that is pretty much what I am doing. SQL is starting under a [quoted text clipped - 49 lines] >> > >> >MG Sue, Thanks again. This time you hit a bit closer. Yes, I was expecting to see non local drives in the database file window so I can put the MDF and LDF on a different network drive. The link you gave me confirms that I just can't do that. Plus, my interpretation of detaching a mdf/ldf file set and putting it on a network share and reattaching it would thus not work either - it is still a network share. Thanks for the help. This resolves it. MG > I'm not sure that is really what you are doing. You keep > referring to mapped drives. You should not be using mapped [quoted text clipped - 71 lines] > >> > > >> >MG |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.