Ask Question Forum:
Model Library:2025-02-08 Updated:A.I. model is online for auto reply question page
C
O
M
P
U
T
E
R
2
8
Show
#
ASK
RECENT
←
- Underline
- Bold
- Italic
- Indent
- Step
- Bullet
- Quote
- Cut
- Copy
- Paste
- Table
- Spelling
- Find & Replace
- Undo
- Redo
- Link
- Attach
- Clear
- Code
Below area will not be traslated by Google,you can input code or other languages
Hint:If find spelling error, You need to correct it,1 by 1 or ignore it (code area won't be checked).
X-position of the mouse cursor
Y-position of the mouse cursor
Y-position of the mouse cursor
Testcursor
caretPos
Attachment:===
Asked by pma111
at 2024-07-20 13:54:58
Point:500 Replies:5 POST_ID:829043USER_ID:10
Topic:
Miscellaneous Databases;;MS SQL Server
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.
If its purely performance risk... why doea storing both on the same drive cause performance issues.
Expert: duncanb7 replied at 2024-07-30 10:28:42
Thx for your pt
ve a nice day
Duncan
ve a nice day
Duncan
Expert: Qlemo replied at 2024-07-21 09:45:55
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).
In addition to that, logfile writes may not be buffered (need to be write-thru), and the DBMS usually forces that (MSSQL does).
Assisted Solution
Expert: ScottPletcher replied at 2024-07-21 09:31:26
166 points EXCELLENT
>> 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.
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.
Assisted Solution
Expert: Qlemo replied at 2024-07-20 14:29:37
167 points EXCELLENT
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).
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).
Accepted Solution
Expert: duncanb7 replied at 2024-07-20 14:04:44
167 points EXCELLENT
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
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
