|
|
Posted by Erland Sommarskog on 11/28/14 11:58
(billmiami2@netscape.net) writes:
> By the way, we discovered that this problem is occurring not only with
> the member listing procedure but also a member search procedure when an
> address search option is selected. Other search options do not cause
> problems. Therefore, I am beginning to suspect that something is wrong
> with our address table. Perhaps we have some fragmentation in an index
> or something related.
You can examine fragmentation with DBCC SHOWCONTIG. But I would not expect
that to be the problem, since you apparently get different plans.
But statistics may not be current. By default, SQL Server updates statistics
automatically, but for large tables it may not be often enough.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|