you can delete the maintenace plan from SSIS instead.

Been there before ...

views of views of views of .... --- Usually a very BAD Idea!

Just my $0.02

You need to change "Security audit to All". On Server Properties (Security Tab)

That's life in the forums

The actual issue is that your stats and IO subsystems may have been impacted by "other" factors.

Example:

1. In a production machine you could have been blocked by some other...

can you post the results of this query:

select serverproperty('Edition'), serverproperty('ProductLevel'), serverproperty('ProductVersion')

I ran your scripts and I get no problems on Development Edition (x64) SP2

When you get an ACCESS_VIOLATION you must contact PSS.

TRUNCATE_ONLY should *always* be your "LAST RESOURCE". Create an appropriate maintenace schedule to deal with the log space. That is the right way

Cheers,

...

Apparently you are having this issue:

http://support.microsoft.com/kb/883415

Are you on SP4 ?

just keep in mind that the "wide index" can not be wider than 900 bytes

and SHUTDOWN always cleanup very well

dbcc shrinkfile ('logical_log_file_name', size-in-MB )

Ok lets see if this helps:

1. *if* those objects are tables you should be able to know the spids that created them by using "sys.dm_tran_locks" or "sp_lock" (check dbid =...

Well I have to admit you are "right".

M$ removed the ability to alter system messages to "logged" . It has been posted in the connect site for a long time...

Changing the password in Config manager should be enough as long as you are not changing the account!