Call Product Support and open a case, you're getting SQL dumping stack dumps, this is potentially a severe problem.

Yes! Get them young, indoctrinate them early. 😀

Please post the full, complete and unedited output of the following.

DBCC CheckDB(<database name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

Do you have a clean backup?

Krishna1 (6/20/2013)

---

Dear Gail

Thank with the script given it working fine. I was trying through SSMS and it was creating the issue. Dont know whats going wrong when i try it...

Yes, it will. The rollover's not for restarting the job, it's for running the...

Could also maybe see error 605

You don't need to create a database before restoring a backup. Just do the restore don't waste time creating a DB just to over write it.

CREATE DATABASE TestingRecoveryModel

GO

ALTER DATABASE TestingRecoveryModel SET RECOVERY SIMPLE

GO

BACKUP DATABASE TestingRecoveryModel TO DISK = 'C:\Databases\Backups\Testing.bak'

GO

USE TestingRecoveryModel

GO

create table a ( a1 char(1000) default 'a1',

a2 char(1000) default 'a2',

a3 char(1000) default 'a3',

a4 char(1000)...

DBCC OPENTRAN

Also checked the log_reuse_wait_desc (select name, recovery_model_desc, log_reuse_wait_desc,* from sys.databases where name in( ..)) it...

Either the backup is damaged or the network returned incorrect data for the backup.

Try getting a fresh backup, copying it local and restoring again

Yes, and it's trivial to test and prove.

Fine, when it works and when it's better than what the optimiser...

Hang on...

If you need to audit 24/7/365, why are you running the trace every 5 minutes? Set a larger file size, set a rollover (BoL will show you how to...

What do you mean by 'active transaction log'? There's always a portion of the log that's active.

If you want to check log behaviour:

Create one database switch it to simple recovery...

That means you just switched to simple and a checkpoint hasn't occurred. The wait types don't change instantly, run a checkpoint and the Log Backup will disappear.