February 9, 2009 at 12:15 am
hi m getting Page Latch 6:1:0 wht shud i do ..... how do i bring this down...
February 9, 2009 at 2:50 am
add more tempdb files.... and check.. depends on ur server and ur activities..
February 9, 2009 at 10:55 am
saby (2/9/2009)
add more tempdb files
TempDB is database ID 2, not database ID 6
samsql: Are you getting latch waits? What's happening at the time? Can you post full message if there's any error message
Page 0 of file 1 of database 6 is the database header page. The only time it should be read is when the database is opened. Unless the DB has autoclose on, that should only be when SQL starts
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
February 9, 2009 at 9:35 pm
m not getting ny error gail but wen i run sysprocesses and check
show me this
Page Latch 6:1:0 and 2: some numbers
so is there ny issue with it bcoz i hav seen due to this my server activity gets slow
February 9, 2009 at 10:26 pm
hi gail m getting this values ...
..PAGEIOLATCH_SH 6:1:332096
PAGEIOLATCH_EX 2:1:6496
February 9, 2009 at 10:40 pm
When an SPID is waiting for an I/O page latch, you may notice that the blocked column briefly reports that the SPID is blocking itself. This behavior is a side effect of the way that latches are used for I/O operations on data pages...
February 10, 2009 at 12:47 am
Sam,
As said above, DB Id 6 refers to User database. You can check this url for details on latch wait types.
Here goes explanation for wait types given :
PAGEIOLATCH_EX --> Resource Waiting on an exclusive buffer latch when the buffer is an IO request
PAGEIOLATCH_SH --> Resource Waiting on a shared buffer latch when the buffer is an IO request.
You should expect some waits on a busy system. This is completely normal and doesn't necessarily translate into a performance issue. Wait events become a problem if they tend to be consistently long over a significant period of time. For example, waits that take few milliseconds over a 2 hour monitoring window are not concerning. Those waits taking over 15 minutes over a 2 hour monitoring window should be investigated more closely.
Try to run Disk Repair utility to check the status of your disk and also check for any hardware failure. May be you can change disks or move the same database to different server and check whether you are getting same error.
Please post when you are getting this error? Like during backup or during Services Start.... It will give a clue of what is happening!
Regards,
Sakthi
My Blog -> http://www.sqlserverdba.co.cc
February 10, 2009 at 8:16 am
samsql (2/9/2009)
hi gail m getting this values .....PAGEIOLATCH_SH 6:1:332096
PAGEIOLATCH_EX 2:1:6496
Latch waits? What's the wait time on them?
IO latch waits are indicative of IO bottleneck. What's the layout of your IO system? What files are where? What raid level?
What do the following perfmon counters look like?
Avg sec/read
Avg sec/write
% idle time
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 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply