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
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
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 declaration syntax
: 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, but we do this periodically to keep things
straightened up.
What we've seen in the past when dealing with SQL
Server
Title: messed up indexes in sql server
I'm really kind of stuck on this one and it's a bit out of my realm, but we really need to find a solution. Basically, a query that's been basically been running fine on the dev server was moved to the production server along with a few database changes,
