Re: SQL Server Can Not See Shared Drive

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

On Thu, 24 Aug 2006 08:02:02 -0700, MG
<MG@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

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

.

Relevant Pages

  • Re: Issues creating a new failover cluster on the same server
    ... G:\Microsoft SQL Server\MSSQL.1 ... CHNSQL04 Cluster Group ... Drives: H and F ... Group, the MS DTC Group, and each of the SQL Server Instance Groups running ...
    (microsoft.public.sqlserver.clustering)
  • Re: Device on Mapped drive
    ... there is a reason SQL doesn't support NAS and mapped drives. ...
    (microsoft.public.sqlserver.setup)
  • Re: Filegroup recommendation
    ... >>> filegroup, and the transaction logs into their own filegroup. ... >>> and multiple hard drives. ... In a multiple-processor system, SQL Server ...
    (microsoft.public.sqlserver.server)
  • Re: Worst monday of my life - please help...
    ... If that's the case, restoring the SQL ... but it finally did install with a few hiccups. ... >> or just leave the mirrored drives in the server on the secondary IDE ... I decided it was time to re-add the mirror. ...
    (microsoft.public.windows.server.sbs)
  • Re: N+1 Configuration
    ... Jasper Smith (SQL Server MVP) ... But looking in the cluster admin tool, ... mounting all other drives under that drive ...
    (microsoft.public.sqlserver.clustering)