Also, look into a few of the other DBCC commands that force the database
to check itself and reset the statistics. I think DBCC Statistics or
something like that will regenerate the statistics for each table.
Since your production tables may have a completely different ratio of
inserts/deletes
al Message-
> From: Chris Stallo
> To: [EMAIL PROTECTED]
> Sent: 11/30/02 6:19 AM
> Subject: Re: [KCFusion] messed up indexes in sql
> server
>
> Have you tried doing a reindex of the entire
> database?
> DBCC REINDEX I think. I realize this takes quite a
> while
Title: RE: [KCFusion] messed up indexes in sql server
I had looked at the reindex command, but wasn't prepared to do one for each index as the syntax appeared, but that command without any other attributes will reindex the entire db? I've also never seen the runtime index declarat
Have you tried doing a reindex of the entire database?
DBCC REINDEX I think. I realize this takes quite a
while, but we do this periodically to keep things
straightened up.
What we've seen in the past when dealing with SQL
Server is the stored procs are using the correct
indexes on the develomen
