I reset the status of the database in question and then placed it in emergency mode to run a checkdb with just error-msgs and got back thousands of errors (7MB worth in a text file so I won't post it here).

My boss wanted to try the REPAIR_ALLOW_DATA_LOSS first before restoring from the backup and we tried that...it ran for 25 mins when I was instructed to kill it. It's been rolling back for the past hour.

EXEC sp_resetstatus 'COREAUTH';

ALTER DATABASE COREAUTH SET EMERGENCY

ALTER DATABASE COREAUTH SET SINGLE_USER WITH ROLLBACK IMMEDIATE

DBCC CheckDB ('COREAUTH', REPAIR_ALLOW_DATA_LOSS)

ALTER DATABASE COREAUTH SET MULTI_USER

We're obviously going to go ahead and just restore from the backups, but I can't do anything until this rollback completes...it's taking forever and we don't need to worry about it anymore as we're going to blow away the DB with the recovery process, can i force this to stop somehow by restarting the services or will i still have to wait for the automatic checkdb to complete upon the service start up