SQL .mdf/ldf files on different server than SQL is loaded?

[squirleegirl]

Greetings!

I've got a piece of software that uses MSDE and does not play well when on the same machine as SQL Server. I moved the software to a different machine, BUT, we already allocated the disk space for this software to the other machine.

Is is possible to have the mdf/ldf files on a different machine and access them through the network? I tried to use the \\server\path address of where I want the files to be on the database properties, but it said it was invalid.

Is there anything else you have to do?

Thanks.

 

[SQLBill]

To my knowledge the .mdf and .ldf files must be on the same server as the SQL Server install. They can be on different DRIVES, but it must still be the same server.

-SQLBill

 

[SonOfEmidec1100]

I believe you can use a MOUNTED drive, windows help tells how to MOUNT an NTFS folder as a drive. (Which is more than I can do).

 

[MDXer]

mounting the drive might work but depending on network on the network and network activity it could be dog slow. You also have the problem that if something happens to the server you mounted the drive from your app would be virtually useless. Unless the database is going to be extremely large it might be more hassle than it is worth.

"Shoot Me! Shoot Me NOW!!!"
- Daffy Duck

 

[nigelrivett]

It can be done and I've seen it work for a time but it's prone to errors and corrupted databases (and server) and such - not something you would want to do if you want to rely on it.

======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.

 

[fluteplr]

Have you tried just loading the MSDE database into SQL Server. They are basically code compatable. Unless the client software is doing something weird it probably won't even notice.