Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
DBA007
Posting Yak Master
145 Posts |
 Posted - 2010-02-03 : 13:17:12
|
| Team,My MaintenancePlan has failed today with stating the error as Executing the query "UPDATE STATISTICS [dbo].[ItemLogitech] WITH FULLSCAN" failed with the following error: "A severe error occurred on the current command. The results, if any, should be discarded.A severe error occurred on the current command. The results, if any, should be discarded.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-02-03 : 14:02:34
|
| [code]DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS[/code]--Gail ShawSQL Server MVP |
 |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-02-03 : 14:03:46
|
| Do you have a particularly bad IO subsystem or something? Because nearly every post is a corrupt DB, a backup failure or similar. Personally, I'd be really concerned at this point if those were my systems.--Gail ShawSQL Server MVP |
|
|
|
DBA007
Posting Yak Master
145 Posts |
Posted - 2010-02-03 : 15:48:07
|
| Gail,the Maintenanceplan and the dbcc freeproccache both run at a time,but today only i got this problem and i found there are no error msgs by dbcc checkdb |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-02-03 : 16:27:47
|
| DBCC FREEPROCCACHE? Why are you running that?Is there anything in the SQL error log?--Gail ShawSQL Server MVP |
|
|
|
DBA007
Posting Yak Master
145 Posts |
Posted - 2010-02-03 : 16:39:18
|
| except this i found nothing.SQL Server has encountered 756 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [d:\sqldata\tempdb.mdf] in database [tempdb] (2). The OS file handle is 0x000000000000089C. The offset of the latest long I/O is: 0x00000090b80000 |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-02-04 : 04:28:02
|
| Speak to the server admins. You've got a very slow IO subsystem (or something else is using a lot of disk bandwidth)--Gail ShawSQL Server MVP |
|
|
|
|
|
|
|
|
Update Statistics error 1073548784