February 8, 2008 at 11:55 am
Hi,
In my company we have 3 drives (don't know if they are raids/ or whatever).
A, B, C drives lets call it that way.
All our databases data are in A drive.
All our databases logs are in B drive.
Question: Tempdb , should the data and log be in C drive or
the Tempdb data be in A drive and the Tempdb log be in C drive?
February 11, 2008 at 7:58 pm
A little more information if you please:
Are the O/S and program files located on any of these drives?
Does this instance host more than 1 database (other than the system databases)?
Speaking of system databases, which of the drives has those data and log files?
Is the database(s) read-intensive or write-intensive or both?
If you could tell us the RAID level for each of the drives it would be valuable also. Your server techs should be able to give you that information quite easily.
- Tim
- Tim Ford, SQL Server MVPhttp://www.sqlcruise.comhttp://www.thesqlagentman.com http://www.linkedin.com/in/timothyford
February 11, 2008 at 8:00 pm
Oh, one more thing, are these drives SAN-attached?
- Tim
- Tim Ford, SQL Server MVPhttp://www.sqlcruise.comhttp://www.thesqlagentman.com http://www.linkedin.com/in/timothyford
February 13, 2008 at 10:29 am
Hi,
The operating system files are on a different letter drive. It is not SAn-attached.
Don't know anything about RAids neither does the net guys.
It is read-intensive. The master and model are on the c (data and logs).
February 13, 2008 at 10:54 am
tempdb data files should be in their own drive, preferably separate spindle.
Log can be placed in the same drive as the other log files.
create as many tempdb data files as there are CPUs. Create them equally sized, with 0 autogrowth. Autogrowth can severely affect your app performance. Ideally, you want the total size of the tempdb data files to be slightly smaller than the total drive size - minus a couple GB.
Don't put anything else in the tempdb drive, if you can spare it. tempdb needs its own exclusive drive.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
February 13, 2008 at 11:25 am
My understanding of the issue is not to have the Tempdb files on the C drive. What I have done is to move the Ldf file to the log drive with the rest of the databases, and the mdf to the data drive with the rest of the database. In our enviorment this is working quite well as our database servers are each one Terabyte in size and have not yet gone to a san. To start adding more temp instances for our size enviorment would be over kill, so I believe that Maria you are working with multi-terabyte systems that would be best handled in your manner. Am I mistaken?
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply