Thanks for the quick response!

I just looked and one of the two indefinite 100% CPU dbs has 20 manual
backups and the other has 44 automated backups which are created hourly with
the oldest deleted. Those hourly backups are stored on the RAID array. That
same db also has daily backups made to another drive on the same server just
in case the RAID gets scrambled (I've only seen that happen once but I HAVE
seen it happen!). All other databases only have daily backups on the
non-RAID drive including the other indefinite 100% CPU db.

I'm in the middle of another project that just got dumped on me so I have to
put this issue on hold for now but I think that you are on the right track
because it would make sense for the 'production' db with many backups vs. a
renamed copy of the db with no backups.

I suppose in a pinch, I could restore a problemed db using a different name
and then change the connection string in the web application accordingly.
There really isn't a need right now but you know Murphy's Law; someone will
call with an urgent need to restore a db from a backup (extremely rare) so I
just want to have a contingency plan if and when it happens.

If I come across the cause and figure out a solution, I'll post a new
message on this board.

Thanks again for your help.

David