Solved

database and log files on same drive

Posted on 2014-07-20
5
304 Views
Last Modified: 2014-07-30
What are the risks in storing the db and logfiles on the same drive.

If its purely performance risk... why doea storing both on the same drive cause performance issues.
0
Comment
Question by:pma111
  • 2
  • 2
5 Comments
 
LVL 13

Accepted Solution

by:
duncanb7 earned 167 total points
ID: 40207839
Database recovery is concern.
Seperate it that is better and same drive Risks reported at this site
http://support.microsoft.com/kb/2033523

and you can take  a look at relative link for reference only if have time at
http://technet.microsoft.com/en-us/library/aa996891(v=exchg.80).aspx

Duncan
0
 
LVL 68

Assisted Solution

by:Qlemo
Qlemo earned 167 total points
ID: 40207867
Both reliability and performance are the reason for separating.

It does not make sense to use two partitions on the same physical disk - if it fails, both partitions are bad, and all files lost. For reliability you try to have a datafile backup and logfiles or a datafile and logfile backups available all the time.

More, neither DBMS I/O subsystem nor the OS I/O subsystem can optimize access for different partitions as good as for a single one. In general, the drive heads have to move much more in such cases.

With DBMS datafiles and logfiles use different access methods. While logfile operations tend to be more sequential and equally read/write, datafiles are read and written in a more random manner, with usually much more reads than writes.
It makes sense to use a file system adapted to those needs - and that is a different one for each.

Using RAID with redundancy (10 or 5 or similar) lessens the importance of separating files. On a RAID 10 you can place both file types into the same file system without risking performance or reliability (to a certain extend).
0
 
LVL 69

Assisted Solution

by:ScottPletcher
ScottPletcher earned 166 total points
ID: 40209456
>> While logfile operations tend to be more sequential and equally read/write <<

Log file operations are overwhelmingly write, not an equal mix of read and write.  That is why RAID5 is not a good choice for log files.
0
 
LVL 68

Expert Comment

by:Qlemo
ID: 40209492
Of course. I forgot that reading logfiles happens in memory most of the time, different from starting MSSQL.
In addition to that, logfile writes may not be buffered (need to be write-thru), and the DBMS usually forces that (MSSQL does).
0
 
LVL 13

Expert Comment

by:duncanb7
ID: 40229738
Thx for your pt

ve a nice day

Duncan
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Shadow IT is coming out of the shadows as more businesses are choosing cloud-based applications. It is now a multi-cloud world for most organizations. Simultaneously, most businesses have yet to consolidate with one cloud provider or define an offic…
This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
Via a live example, show how to extract information from SQL Server on Database, Connection and Server properties
Viewers will learn how to use the INSERT statement to insert data into their tables. It will also introduce the NULL statement, to show them what happens when no value is giving for any given column.

919 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now