EM and QA not returning the same results | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

EM and QA not returning the same results

Hey guys- Has anyone seen this one before?
I right click a table in EM and select Open Table>Return all rows. My result set is about 5,000 records. I run the same in Query analyzer(Select * from MyTable) and get 36 rows returned. I verified more than once that I am examining the same table on the same DB(not confusing Development with Production). I was looking at this because of an error during the reindexing process, which is another post entireley. Any help would be good. Thanks!
I pressume QA is the right answer. Since EM is GUI tool sometimes show wrong information.
But, to be honest, I never see something like this. Luis Martin
Moderator
SQL-Server-Performance.com One of the symptoms of an approaching nervous breakdown is the belief that one’s work is terribly important
Bertrand Russell
All postings are provided “AS IS” with no warranties for accuracy.
Yes QA is the right answer.
I had this issue. but when I isntall new sp I got away with this issue —————————————-
http://spaces.msn.com/members/dineshasanka

I came accross the same situation some days before,
Once I tried , "EXEC sp_updatestats " I did this, even my "auto update statistics" option is on. it is resolved after I applied sp_updatestats. I think bulk deletions might not reflected with the table. -Johnson
I think EM uses the column rowcnt in sysindexes, while QA, well, actually, counts the rows. rowcnt can get out of synch and usually a sp_updatestats or a sp_spaceused @updateusage = true will resolve this issue. —
Frank Kalis
Microsoft SQL Server MVP
http://www.insidesql.de
Ich unterstütze PASS Deutschland e.V. http://www.sqlpass.de)

The strange thing is that EM returned 5000 rows, not just info that there are 5000 rows in the table. At least that is my understanding of original post. However error during reindexing is probably related to the issue.
Even in QA in order to get correct results sometimes you need to run DBCC UPDATEUSAGE and the way mentioned above. But never trust EM results as it is flaky at times and I always suggest to use QA in order to know what is happening under the carpet. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Few times due to mismatch of MDAC version using client tools will have similar effect, as suggested try to resolve the errors and check the results. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>