September 29, 2009 at 12:30 am
Guys,
I am facing one issue while database files backup.
I am getting the below message when i see the SQL Error log.
I ran the trace no.8033 to disable this error but nothing happed :unsure:
still i am getting this waring /error message.
1. As I am working on development env. both data & log files are kept on same drive.
2. Count of database on same db server...(5) :w00t:
SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [<ldf filepath >] in database [<databasename>] (8). The OS file handle is 0x000000000000097C. The offset of the latest long I/O is: 0x000000006f5400
please help me how could I face the situation :doze:?
Abhijit - http://abhijitmore.wordpress.com
September 29, 2009 at 2:02 am
It means your IO subsystem is not handling the load put on it.
How to make it go away depends on how the system is set up currently. It may require adding more spindles, moving data and/or log files to separate drives, backing up to drives other than the data/log drive, etc. Need far more info on your drive layout than what you've so far given. If it's a development environment where performance is not important then you can possibly just ignore the message
Why do you want to turn a traceflag on to hide the message?
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
September 29, 2009 at 4:08 am
Gail,
I read in one of the article we can turn off the message by running the traceoff flag 803
Abhijit - http://abhijitmore.wordpress.com
September 29, 2009 at 4:23 am
Abhijit More (9/29/2009)
Gail,I read in one of the article we can turn off the message by running the traceoff flag 803
I would seriously advise not playing around with trace flag 8033, it is used for drift warnings and it is not recommended to enable unless you know exactly what you are doing.
Trace Flag 8033
Trace flag –T8033 can be used to suppress the drift warnings. Do not enable this trace flag on Microsoft SQL Server 2005 unless you fully understand the ramifications of ignoring the drift warnings.
and to understand further, the error you are receiving is not a drift warning, as Gail has suggested it is down to the I/O subsystem being over stretched and you can make I/O related changes to fix that. such as moving files and scaling up or out the hardware.
--------------------------------------------------------------------------------------
[highlight]Recommended Articles on How to help us help you and[/highlight]
[highlight]solve commonly asked questions[/highlight]
Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
Managing Transaction Logs by Gail Shaw[/url]
How to post Performance problems by Gail Shaw[/url]
Help, my database is corrupt. Now what? by Gail Shaw[/url]
September 29, 2009 at 11:07 am
Abhijit More (9/29/2009)
Gail,I read in one of the article we can turn off the message by running the traceoff flag 803
That doesn't answer my question. Why do you want to turn the message off?
It's a warning that the IO subsystem is not handling the load. If you don't care, ignore the messages. I don't understand why you want the message not to appear at all.
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
September 30, 2009 at 2:59 am
I have also seen this error occur when a server backup agent, such as NetBackup, is accessing the live database files in order to copy them to tape.
I don't know if your using anything like NetBackup on this dev server but check anyway.
If you are, make sure the live database files (data & log) are excluded from the server backup, but also make sure you database backups are included.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply