SQL SERVER 2000 - see mapped drives

[kizziebutler]

I have mapped drives to a sql server 2000 machines and I was wondering if it is physically possible to make sql 2000 to see mapped drives. I know he can see physical drives.

 

[fredericofonseca]

what are you trying to do exactly?

SQL server will see all drives that are available to the account that is used by the SQL Server instance to login to the local machine.

So if you have a map to \\john\cdrive, and you are using a local account RITA, then you need to give permissions to RITA to access share \\john\cdrive.

The same applies to jobs running through SQL Server Agent. Whatever user is used for the Agent (which is not necessaraly the same as the SQL Server instance), needs to have the proper permissions granted to him.


Regards

Frederico Fonseca
SysSoft Integrated Ltd

http://www.syssoft-int.com

 

[kizziebutler]

I am running out of space so what I want to do it mapped some drives to the server I have logged onto. I want to create a database and point the database files to the mapped drives but it only sees the physical drives when you try and point the database to the mapped drive.

 

[gmmastros]

MIcrosoft doesn't support attaching to a database on a mapped drive. In my opinion, you should spend a couple dollars and buy another hard drive for the computer.

-George

Strong and bitter words indicate a weak cause. - Fortune cookie wisdom

 

[hmckillop]

I think you can use a DBCC command to switch of the restrictions to allow you to use UNC network directories.
However, seriously consider your actions first, there will be serious performance issues and also integrity if even a blip occurs on the network.
SQL has this option switched off as default for very good reason.

Anyway I think it is

DBCC TRACEON 1807

But check on other forums

http://www.sql-server-performance.com/ac_sql_7_traceflags.asp

http://www.extremeexperts.com/SQL/Articles/DBCCTraceFlags.aspx

"I'm living so far beyond my income that we may almost be said to be living apart

 

[mrdenny]

If you are going to put databases on a remove machine (which you shouldn't do for network reasons) don't use a mapped drive, use the full UNC path to the network share.

Mapped drives can be changed easily and can be marked as unavailable by the OS which would kill your database.

As gmmastros said, it's MUCH better to by more hard drives.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

Donate to Katrina relief

 

[kizziebutler]

This is only a temporary solution, a copy of the database is going to be used for testing purposes for a couple of days and a mapped drive is the only available space I have with disrupting the live database. I have tried the dbcc traceon(1807) on the master database but it does seem to work. If you create the database a UNC path does not work or the mapped drive is not seen to reside the new database file on creating, database.mdf and transcation logs. Any other ideas!!!! This is only temporary so performance will be kept to a minimum, for testing purposes only.

 

[hmckillop]

You cant do it for system databases only user created dbs.


"I'm living so far beyond my income that we may almost be said to be living apart

 

[kizziebutler]

that is what i am trying to do. I create my database and it does give me the option to select the mapped drive or use unc path.

 

[mrdenny]

You won't see any change inthe UI. You'll need to create the database via code and manually type in the UNC paths in Query Analyzer.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

Donate to Katrina relief