Shawn,

It's a shot in the dark but just for kicks, I would have a look at the following:
Owner of DB in old system vs. new system
Useres of DB in onld system vs. new system
DB config (trunc on checkpoint, bulk copy, etc.)

(The following may have changed - it has been a while since I verified it) When you create a new db and restore from a backup, the owner of the DB does not restore as this information is stored in the master db. (I don't think that this is the case anymore: In addition, any users of the server do not restore and the users of a DB are related to the users of the system by uid. uid is dynamically generated so if you do not add your users on the new server in the same order as on the old, they may not match up with your restore.)

If your coders were very specific about the owner of the index, etc, you could have created new ones. (for example if you are no longer DBO, and the code checks for the existance of the indexes using a fully qualified path db.owner.table - and creates them if they don't exist, - it could have caused the symptoms you describe.

At the very least, I suspect that you will want to update statistics on all your tables.

. . . Tom

Tom Zeblisky
Reuters


On 06/17/2002 10:27:00 AM Shawn Smith wrote:
> I have an application that runs a report. It has ran fine for years. We
> implemented a new prod server and restored from a backup. All other
> applications that we have ran they run fine, except this one. The job filled
> up TempDB and appears to run until it does, 12 GB worth. This tells me it
> might be an index, so I ran a count on sysindexes and have gained 30 indexes
> . I think it happened in the restore...how do I find the problem?
>
> Shawn Smith
> Database Administrator
> Fort Worth Star-Telegram
> 817-390-7094
> 817-291-5240 cell
> 817-667-2757 pager
> [Email Address Removed] Visit our Internet site at http://www.reuters.com

Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of Reuters Ltd.
MS Sql Server LazyDBA home page