Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / DB Engine / SQL Server / March 2008

Tip: Looking for answers? Try searching our database.

Move Temp DB and Logs to get more speed?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Bishop - 11 Mar 2008 21:15 GMT
We are running a server with IIS and SQL 2K using the following
configuration:
C: OS/Inetpub
D: SQL 2K DB/Logs
E: IIS Logs
F: Not Used
G: Not Used

We have a single SQL 2K DB that all the websites use.

I'm currently constrained to a single server and the drive configuration.  I
would like to optimize better by using the new F: and G: drives.
Additionally the C: and D: have no problem keeping up so I could move IIS
logs to the C: drive if needed.

Based on reading I've been doing it sounds like I will get the best
performance from moving the TempDB and the Logs files to different drives
but which configuration would be best:

F: TempDB DB and Logs
G: Our main DB Log Files

or

F: TempDB Logs
G: Our main DB Log Files

or

Something else.

Please suggest my best route.

Thanks!
Tom Moreau - 11 Mar 2008 21:28 GMT
It's a best practice to have the data and logs on separate partitions.  This
is both for safety (High Availability) as well as performance.  Also, try to
keep tempdb separate from your app DB's.  Thus, you could go with:

D: app data
F: app log
G: tempdb

Try that first.  You can also move the tempdb log to F: and see if that
improves or degrades performance.  Logs should not be placed on RAID5
partitions.

HTH

Signature

  Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON   Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau

We are running a server with IIS and SQL 2K using the following
configuration:
C: OS/Inetpub
D: SQL 2K DB/Logs
E: IIS Logs
F: Not Used
G: Not Used

We have a single SQL 2K DB that all the websites use.

I'm currently constrained to a single server and the drive configuration.  I
would like to optimize better by using the new F: and G: drives.
Additionally the C: and D: have no problem keeping up so I could move IIS
logs to the C: drive if needed.

Based on reading I've been doing it sounds like I will get the best
performance from moving the TempDB and the Logs files to different drives
but which configuration would be best:

F: TempDB DB and Logs
G: Our main DB Log Files

or

F: TempDB Logs
G: Our main DB Log Files

or

Something else.

Please suggest my best route.

Thanks!
Bishop - 11 Mar 2008 21:46 GMT
Hi Tom, thanks for the advice, just to clarify are you suggesting moving
both TempDB Data and Log to G to start or just the Data?

> It's a best practice to have the data and logs on separate partitions.
> This
[quoted text clipped - 47 lines]
>
> Thanks!
Tom Moreau - 13 Mar 2008 02:33 GMT
Initially, try both data and log for tempdb.  If that is satisfactory, you
can leave it.  If you still have perf issues, then move the log to another
drive.

Signature

  Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON   Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau

Hi Tom, thanks for the advice, just to clarify are you suggesting moving
both TempDB Data and Log to G to start or just the Data?

> It's a best practice to have the data and logs on separate partitions.
> This
[quoted text clipped - 47 lines]
>
> Thanks!
Bishop - 14 Mar 2008 19:24 GMT
Changes worked great!  Thanks for the recomendations.

> Initially, try both data and log for tempdb.  If that is satisfactory, you
> can leave it.  If you still have perf issues, then move the log to another
[quoted text clipped - 54 lines]
>>
>> Thanks!
Tom Moreau - 19 Mar 2008 14:14 GMT
Great news.  Thanx for the follow-up.  :-)

Signature

  Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON   Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau

Changes worked great!  Thanks for the recomendations.

> Initially, try both data and log for tempdb.  If that is satisfactory, you
> can leave it.  If you still have perf issues, then move the log to another
[quoted text clipped - 20 lines]
>>
>> HTH
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.