Most likely someone's switched the DB to simple recovery and back to full since the last full backup. As such, there's no current database backup to base the transaction log...

I would have some doubts about that BoL page, never seen a minimally logged operation trigger a checkpoint before and besides, it doesn't need to trigger a checkpoint. Any data...

As I said

You have 32 GB of memory in that machine. If you add the /3GB, you will limit...

How did you drop the statistic? How are you seeing that it's still there?

Please read through this - Managing Transaction Logs[/url]

/PAE needs to be in the boot.ini, not /3GB, or IncreaseuserVA

And if they have sysadmin permissions, you have larger problems than a DDL trigger, they could drop the database, shut down SQL, steal a backup, change data, etc.

Minimal permissions!

Short of profiling the instance, I don't think you can tell which session created which table. You can see the temp space that each session uses with the sys.dm_db_session_space_usage DMV.

There has never been a guarantee that a select without an order by will return the data in any particular order, whether it be insert order or anything else. It...

Administrative tools -> Local...

Probably instant file initialisation.

How do you know it's not on? Checked the local security policy setting? If SQL's running as admin, could be that someone gave the administrators group...

Query sys.dm_exec_cached_plans, cross apply to sys.dm_exec_sql_text and search for the text matching the ad-hoc query.

You've given the same physical file name to all three of the data files. They need to all be different physical files, so each of the data files needs a...

Then just switch to simple recovery, switch back to full immediately, run a full backup and restart the log backups after that. Providing there's nothing else preventing log reuse, that...

That's not a standard job. As your client what it does or open in in maintenance plan editor and take a look. As for why it's failing, take a look...