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 : 10:42:40
|
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 |
|
sprobst
Starting Member
5 Posts |
Posted - 2006-07-04 : 10:52:00
|
I know - new to the forum and recognized later that this might be the better place to ask this question. |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2006-07-05 : 18:14:38
|
If you do an UPDATE STATISTICS...WITH FULLSCAN, do they get corrected?Do you have any non-clustered indexes? How many rows are returned if you use one of the nc indexes as the access path for the select count(*)?Paul RandalLead Program Manager, Microsoft SQL Server Storage Engine + SQL Express(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.) |
|
|
sprobst
Starting Member
5 Posts |
Posted - 2006-07-06 : 04:28:11
|
Hello Paul,getting the number of rows from the indexes shows the correct number of rows (meaning it is equal to the returned number of records if doing an select *.) UPDATE STATISTICS...WITH FULLSCAN corrected the statistics but it seems the are not updated automatically correct although this option is set. Besides that our colleaguages at Volkswagen proofed that the Enterprise Manager often shows incorrect information (statistics, open connections, ...) If you directly query the system tables than you get the correct results.So at the moment fortunately it seems that we don't have a real problem besides incorrect information from the Enterprise Manager. No data loss and that is for the moment the important message. (Still have 2 databases with strange results but these are "well known" applications to us - they often crash and this might be the real explanation for the date loss in this 2 databases. But who knows - we are still investigating this as well...) |
|
|
|
|
|
|
|