Seen it with my own eyes...

http://sqlbits.com/Agenda/event5/Let_s_make_SQL_fly___a_technical_session_for_developers_and_administrators_who_believe_in_magic_/default.aspx

OK, you do not have a [Run As] then it is running as the service account.

[Shift Right click] on SSMS, select [Run As], enter the Service Account details,...

Archive off data to a table you can hammer.

Have a the batch size configurable.

Allow time for have processes to obtain a lock

DECLARE @n Int

DECLARE @ROWCOUNT int

DECLARE @msg nvarchar(500)

SET @n =...

check the [Run As] box in the SQL job step. It is probably different from the one you use for SSIS. The step type is also different. Read up on...

check the permissions on [NT SERVICE\SQLSERVERAGENT], i think the upgrade may have removed the service account

If you declare a variable @varchar(1000) it will allocate more memory to the query than varchar(100). This can be a good thing. A field is different, as described above.

time for DBA's to be humble... ahh, we're not masters of the universe.

If you can't trust your System Administrator you are in trouble. If the data was that important you'd also have other controls in place. I don't think this is really...

If your interested this will also help. The status report requires three tables..

USE [DBA_Maint]

GO

/****** Object: Table [SQLStatus].[ServerErrorLog] Script Date: 01/28/2010 11:50:49 ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

CREATE...

This bastardised from a number of different scripts from the internet...

USE [DBA_Maint]

GO

/****** Object: StoredProcedure [SQLStatus].[spDailyHealthCheck] Script Date: 01/28/2010 11:21:19 ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

ALTER PROCEDURE [SQLStatus].[spDailyHealthCheck]...

I tested this, after 2hrs 9 minutes i got he following error:

Msg 8164, Level 16, State 1, Procedure sp_get_composite_job_info, Line 72

An INSERT EXEC statement cannot be nested.

Mail queued.

It sounds like you already have set the distributor up. Skip Step 1a and start from 1b.

Ask SSC works!! DBCC SHRINKFILE ('LogicalFileName',40000), set the specific size and it goes below the initial size.

Have you tried putting a WITH REPLACE in the RESTORE statement?

test connectivity...

telnet xxx.xxx.xxx.xxx 25