October 22, 2009 at 6:30 am
I was just beginning to have the same thought! Thanks everyone 🙂
February 18, 2010 at 6:05 pm
Pity no resolution note is visible ...
Just discovered this happening on our brand new SQL2005 64-bit Standard installation.
Every morning at about the same time IO takes longer than 15 seconds.
The entire server is not used at all except for testing ETL - which is in full flight when this happens doing transforms to populate the 3rd largest table in the Data Warehouse - a 6GB table in a 100GB data file.
The exact same process happened previously on this machine when it was a 32-bit server with SQL2005 Std 32bit and never got this error. What our IT team did was reinstall Windows2003 as 64-bit and SQL2005 as 64-bit. Would there be any link to the 64-bit version of SQL2005?
February 18, 2010 at 6:50 pm
Ol'SureHand (2/18/2010)
Pity no resolution note is visible ...Just discovered this happening on our brand new SQL2005 64-bit Standard installation.
Every morning at about the same time IO takes longer than 15 seconds.
The entire server is not used at all except for testing ETL - which is in full flight when this happens doing transforms to populate the 3rd largest table in the Data Warehouse - a 6GB table in a 100GB data file.
The exact same process happened previously on this machine when it was a 32-bit server with SQL2005 Std 32bit and never got this error. What our IT team did was reinstall Windows2003 as 64-bit and SQL2005 as 64-bit. Would there be any link to the 64-bit version of SQL2005?
Again there are MANY issues that could be at fault here. Among them: firmware, drivers (this is most likely IMHO since 64bit drivers have been updated regularly over the last few years and you could be using an outdated one), server settings, sql server settings, IO configurations, someone created DBCC and backup jobs that run at same time, phase of the moon . . . 😀
Once again we can go back and forth hunting and pecking for a cause - or you can have someone remote in and find the answer quickly and efficiently.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
February 19, 2010 at 6:22 am
This is one of the most difficult things to figure out what is the culprit. I know from experience. I even envolved Microsoft Premiere Support. We were never able to find what was wrong in our situation. We migrated the databases to a newer SAN and the problem went away... No one knows what the culprit was though.
February 19, 2010 at 8:53 am
We were seeing these errors as well.
We checked out the SAN - all clear.
Once we stopped Diskeeper 2010 with Hyperfast (build 14.0.900.0), the errors stopped.
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply