We help IT Professionals succeed at work.

How to install SQL 2008 Log and Data on seperate servers?

macpiano asked
Seems like this would be documented all over the place but it is not easily found. I have 3 servers and I want to put SQL itself on the OS server, data on another, and log on a 3rd. When it asks for these locations it wants a drive letter. Obviously another server is not going to do that unless I persistently map a drive to that other server on startup.

What is the correct syntax to hit the other server and does it have to have a named folder on the 2nd and 3rd server?

Watch Question

"Batchelor", Developer and EE Topic Advisor
Top Expert 2015
That is not supported at all! MSSQL requires both data and log files to be on the same server as the DBMS software. Anything else will lead to damaged files eventually.
Lee W, MVPTechnology and Business Process Advisor
Most Valuable Expert 2013

You can do this... not the way you would expect... but you can do this...

You would need to install iSCSI target software on the two servers that DO NOT run the SQL server itself.  Then you would need the iSCSI initiator on the machine that has SQL itself installed.

Assuming you have the above, you would "share" out disk space on the two target systems and on the initiator system, you would connect to the space on the other servers - the space would appear as local storage on the initiator system and then you could put the data and logs on those drives.  

But this is rarely (if ever) done and in general - if you're not willing to setup a true SAN for storage, then you don't do this.  Put the data and logs on separate RAID arrays within the same server or buy a real SAN.  I would consider it extremely unwise for you to do this using "Shared" drives ... as Qlemo states, this is NOT SUPPORTED AT ALL and if you were to put a system into production with that configuration and you worked for me... I'd be firing you for doing something unsupported that if we have problems with, we cannot get support.


That is probably why there was not much documentation on this. I'm not a sql guy but can work my way around and I was setting up a sql database server and wanted to make sure I was optimized. I should mention this is all on a VMware server self contained and all partitions are on the same 6 spindles as Raid 1+0 so I figured there would not be any slick way to get more performance.