February 13, 2009 at 4:43 pm
We have 6 or 7 databases set up for logshipping. The MSDB write % is very high compared to all databases, even our main database. Can anyone explain why it would be so great when the database is in Simple Recovery mode? I'm assuming logshipping is the culprit since MSDB is 2GB and the log_shipping_monitor_history_detail table is > 1.5GB.
% ReadsReadsRead Wait Time (ms)Avg Read Wait (ms)
main_db76.24%70456250824257.2
jira0.07%6572422 3.7
LiteSpeedCentral0.05%4956110 12.3
LiteSpeedLocal1.89%1748519404711.1
Maintenance0.01%833884.7
master0.02%1832373 13.0
model0.02%1794932.8
msdb19.33%17862736644849 205.1
% WritesWritesWrite Wait Time (ms)Avg Write Wait (ms)% Total IO
main_db6.44%26550210865530 40.9 19.23%
jira0.00%1881822 9.7 0.02%
LiteSpeedCentral0.05%2096 5173 2.5 0.05%
LiteSpeedLocal39.75%163787516416446 10.0 32.81%
Maintenance0.00%610 1.7 0.00%
master0.03%1290 1543 1.2 0.03%
model0.00%1016 1.6 0.00%
msdb47.07%19396375626323 2.9 41.99%
% ReadsReadsRead Wait Time (ms)Avg Read Wait (ms)
MSDBData99.89%17842836643596205.37
MSDBLog 0.11%19912536.30
% WritesWritesWrite Wait Time (ms)Avg Write Wait (ms)% Total IO
MSDBData6.16%119532298668124.9864555114.07
MSDBLog93.84%182010526396421.45026907885.93%
Thanks,
Scott
February 14, 2009 at 4:36 am
Please don't cross post.
No replies to this thread please. Replies to:http://www.sqlservercentral.com/Forums/Topic657055-360-1.aspx
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply