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 |
sprobst
Starting Member
5 Posts |
Posted - 2006-07-04 : 09:46:14
|
Hello together,strange things going on:1. The table statistic shows for example 67 rows in a table, select count(*) only returns 63 rows.2. Table statistic shows 50 rows, select count(*) returns 55 rows.In both cases if you do an insert the newly inserted row sometimes can be retrieved by a select statement sometimes not. Row statistics sometimes is updated correctly, sometimes not.Integrity check for these databases says everything is fine. DBCC CHECKDB, DBREINDEX, UPDATESTATISTICS, ... does not help or says everything is fine.Already opened a case at HP's Microsoft support and they involved Microsoft itself but all are a little bit clueless at the moment.As this is our main DB cluster and several databases are affected we had to stop most of our applications since last Thursday and now we are getting a little bit in trouble so any hint is very welcome.Thanks in advancePS: Restore is not an option - as all tools say everything is fine all of our backups from the last months include the error. Don't ask why nobody recognized the lost data earlier, seems they were stored but not required for some time. |
|
mr_mist
Grunnio
1870 Posts |
Posted - 2006-07-04 : 10:44:13
|
My wild stabs in the dark are -Try turning off parallel processing and seeing if that improves things.Check the server's memory, it could have a faulty chip.-------Moo. :) |
 |
|
yogeshsr11
Starting Member
2 Posts |
Posted - 2006-07-04 : 19:25:30
|
I wonder if there is a deadlock and some transactions are becoming victims. try setting deadlock priority of INSERTS on this table to high.Yogesh Ranade |
 |
|
sprobst
Starting Member
5 Posts |
Posted - 2006-07-05 : 03:13:03
|
Yogesh, the problem is that half of our databases are affected and we have one important application that creates large number of tables dynamically. Hard to set this option on all affected tables... |
 |
|
|
|
|