Saving the table, as suggested above is the best idea. Backup & restore (to another DB name I assume) is overkill for this application.

Not quite, but maybe I can tweak it a bit,

That was easy ! Thanks. I must have had a mental block thinking it wouldn't work that way because it looks like it's trying to select @FLD4 from...

I'm not quite clear on the problem, but maybe what you're looking for is "STANDBY" instead of "norecovery". then you can run selects because the DB is in read-only, but...

You're right. I should have at...

Phil Auer (11/12/2008)

---

2. I do not have another SQL Server 2000 instance to test on (all others are 2005) and I don't want to play around on my production server....

Is this theoretical or actual ? If actual, then you should already have backups and you can look at the file size. The available space will not be...

FYI, when making changes to data like this, I usually take a few precautions.

1. Back up the table first by creating a copy with a different name, such as:

[font="Courier New"]select...

Perhaps you could explain the environment a bit more & what you are currently doing, then others can make more specific suggestions.

Mike Levan (11/17/2008)

---

I am trying to get users to run it from any DB in the instance to check the Lock Details.

Also how can i test that proc by running...

High CPUTime and DiskIO might just mean that the connection has been open for a very long time and a lot of work has been done. The connection could...

So, it seems that RWA_ID is created by 2 different processes. One increments numbers starting at 6000000000, and another increments starting at 8000000000. A bit strange design, since eventually...

I assume your backups are running from a scheduled job. If so, open the job, open the step, and the backup script should be there with all the specifics.

My bubble has...

First - is everything backed up properly & frequently ?