July 31, 2008 at 11:43 am
Im installing a new SQL 2005 server and the a vendor gave me limited instructions on how they need it setup. They said put the SQL code on d:\ the LDF on e:\ and the MDF on f:\. I have all these drives setup but how in the world do I specify this during the install and what is the MDF and LDF anyway? Please help.
July 31, 2008 at 11:53 am
MDF is your data file and the LDF are the log files. When you walk through the install you can point where you want to put the default datafiles and the log files. Getting there is a bit tricky and you should refer to the documentation as you do the install.
I'm assuming you are going to create the vendor database and when you walk through the database creation you can specify the file locations as well for both the data and the log file. Again, use the documentation.
If you have more questions add them on and I'm sure you will get answers.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
July 31, 2008 at 12:15 pm
I see where to do a "custom" install to decide where to install the master database files but I see no reference for the Log Files. What would that me named in the install list?
July 31, 2008 at 12:38 pm
Somewhere there is a default location for data and log files.
No worries, after you've installed it, you can change this. Right click server, properties, database properties. You can choose the paths at the bottom.
If you've added databases, you can detach them, copy the files, then attach them in the new locations.
July 31, 2008 at 1:02 pm
The big thing is putting your customer database in the proper spot per their recommendations and when you go to create that database you should be able to right click on the database folder in SQL Server Management Studio and it will walk you through creating one. In that process set your location for the MDF and LDF files. You might want to also consider creating folders on the drives for them. Something like the following;
E:\MSSQL\Data
F:\MSSQL\TranLogs
That way the actual database files are not laying around at the root.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
July 31, 2008 at 1:05 pm
The reason for putting them on different drives basically serves two purposes. One, to improve performance by preventing contention for disk resources between the transaction log and data file. Two, to provide isolation should a drive fail.
If your drive letters are on the same RAID(0,1,5,etc) array then those two things aren't accomplished.
For example, if you have a server with 6 drives all configured in a RAID-5 array then it's just as well to put everything on a single drive letter.
Otherwise, a configuration like below would be provide better performance and isolation, at the cost of usable drive space.
Drive 0-1 C: - RAID 1 - OS and SQL
Drive 2-3 D: - RAID 1 - Primary database files (MDF)
Drive 4-5 E: - RAID 0 or 1 - Transaction log files (LDF)
August 2, 2008 at 9:27 am
you wouldbe best to set the default paths after installation.Its a lot easier or use custom scripts to set the paths
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply