Personally, I agree with Jim P. (maybe I would skip diff backups). If you perform log backups every hour and log doesn't get truncated,  check for the last open transactions with DBCC OPENTRAN command...

If by 'access the domain accounts' you mean to be able to use Windows Authentication and authenticate Windows users by querying Domain Controller, it's possible - we've been using...

From my point of view, when situation like this arised (no recent backups, server failure, db corruption), you probably did all that was possible. But I would wait for the...

From what you posted I understand that it was a memory-related problem that brought down the server. What was the output of running DBCC CHECKDB (without repair clauses) ? Was...

You must put yourself one question. How precious is your data? What is your recovery strategy in the event of failure? Is it ok to return to last full backup or is it necessary...

Firts of all, what is the reason for the database to be in suspect mode? check sql server error logs, have you tried to restart the server? are there error...

it all depends on the fact whether your transaction log file is available or not - in other words on the extent of the failure. For example:if your data files...

Does log_xsadmin login exists on the new server? if not create it and run

sp_change_users_login 'update_one' ,'xsadmin','log_xsadmin'

these steps should synchronize syslogins and sysusers tables on the new server.

I'm not sure...

Do you mean database users or sql server logins?

See Books Online topics 'Shrinking the transaction Log', 'Truncated transaction logs' and 'Transaction Log Physical Architecture' for explanation, you can use undocumented command DBCC LOGINFO ('db_name') to view virtual logs...

it seems to be logical rather than physical corruption of system catalog. I'm afraid that there is no easy way out without exposing yourself to potential future problems. The safest...

Have you tried to run DBCC CHECKDB against your dbs? If so what were the results?