WHERE (b.datefield > a.datefield

Doesn't this mean you might get varied results if more than one b.datefield qualifies as > than a.datefield ?

Why not use the JOIN syntax ?

Browse through the "Scripts" area for plenty of useful ideas.

Should probably be a "sticky" at the top of the various Admin forums.

Sometimes the "problem" is that a database is set to FULL RECOVERY, but someone forgot to set up regular transaction log backups (every 15-30 min or so is common).

Another good...

How scrambled do you want the names to be ? You could restore to test, then set all the last names to the same thing, or build a temporary table...

What have you looked at so far ?

Perhaps they are a member of an AD group, and that group has database permissions.

Ideally, you could save the trace data to a flat file on another drive not used by SQL.

ALTER LOGIN [ADSERVER\MYUSER] DISABLE will disable the account for the whole SQL instance

If you want to remove a user from a specific database:

USE [MyDatabase]

DROP USER [MyDomain\ThisUser]

If these are important databases, I would suggest t-log backups more frequently than every hour. Consider the recent thread yesterday of the person who's database failed, so they lost 40...

One risk to removing redundant indexes is they could be referenced as a hint in a stored procedure. You could use something like this to scan your SPs for the...

Did the 11 am log backup attempt to run ?

What service pack are you on ? Sometimes these odd problems occur in early versions, and are fixed in later SPs.

I don't see SETSPN.exe on the server, so maybe server tools are not installed. Perhaps the original problem is caused by the old SQL Services account being a domain admin...

Under SQL ServerAgent, create a new job, then paste your code into a new step within the job. Create a notification to alert you if it fails, then schedule it...