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 |
|
StewTRW
Starting Member
2 Posts |
 Posted - 2008-03-17 : 05:06:32
|
| On Saturday morning, we had a problem with one of our tables.We've experienced this before and it's been fixed by creating a new (random) index and resaving the table from within enterprise manager. The problem is that the table is so slow to be accessed. This is a big problem as our client is a real time logging manufacturing plant which ends up coming to a standstill.This is how two successive rows look. The index (identity) has been incrementing but no rows have been inserted. 3416582 | 2008-03-15 02:27:47.057 3416716 | 2008-03-15 05:12:20.300 I must add that this is a unpatched SQL Server (8.00.194 RTM). Will this issue be fixed when they patch the server? (I'm just a developer, we have sys admins who look after the servers). Many thanks in advance |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-03-17 : 18:43:31
|
| If the identity has been increasing, yet no rows have been inserted, then your transaction is being rolled back due to an exception or other issue. Your application should be receiving an error about this condition. If it isn't, then you aren't properly catching it. I'd suggest running SQL Profiler while an insert is attempted and have exceptions added to the trace. You can then see what is going on.I'd say that this is not a corruption problem as corruption is based upon the output of DBCC CHECKDB.I don't have the service pack fix list memorized, so I don't know if getting it up to sp4 plus the security patches will help your problem. But it is very important that it get patched ASAP as there are performance improvements in them as well as security fixes.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
 |
|
|
StewTRW
Starting Member
2 Posts |
Posted - 2008-03-18 : 06:14:18
|
| Additionally we are getting problems with random SPROCs hanging, in fact this was the original issue and has slowly been replaced by the table index issue. All that it takes to resolve it is to refresh the SPROC with the addition of a comment. Has anyone else had this issue and resolved it?Its a little unsettling given the size and quantity of our tables.For the record, we get Timeout Expired errors in the client application. Thanks for the help in advance. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-03-18 : 13:50:48
|
| You need to get to sp4 before we can troubleshoot performance issues.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|
|
MSSQL 2k Corruption