Hi, This has been driving me nuts for a few days now. I'm more a developer than DBA, but the answer I suspect lies in the Server configuration. Apologies for the length of this, but I have tried a lot of things. Scenario : We get a monthly database dump in the form of a 1.5Gb csv file, comma delimited...

I have an older Dell boxen with 2000 SVR SP4 with SQL 2000 SP4 Our app is getting slower as it ages and the mainboard cannot take more than 1GIG of ram. Without getting new hardware, Id like to use this time to tune the DB before we spend $$ on an upgrade. When I let memory go dynamic, it eats into all...

Indexdefrag does NOT update stats. You need to run: UPDATE STATISTICS TableName WITH FULLSCAN -- WITH FULLSCAN is an option Remember also: EXEC sp_recompile TableName You need to set the table that has updated stats for Recompile. Then ANY sproc that hits that table will recalc its execution plan with...

The stats seem to be the same. The restored db is only a day or so old. The stats get updated on production every morning and the indexes are rebuilt once a week. Our usual weekly reindex is done with a variation on the sp by T.Pullen with the scan density threshold set to 85 http://www.sql-server-performance...