Well perhaps it just can go that high. I changed it to 2 MB which is sufficient for my issue and it worked.

Exec sysmail_help_configure_sp

EXECUTE msdb.dbo.sysmail_configure_sp

...

I'm running into this same problem. I changed the default to be 9 GB since my exchange environment has a 10GB limit. I am still getting the same...

Yes, with further testing I realized that SQL Server 2000 through SQL Server 2008 R2 all did the samething. This changes the question slightly.

How does SSIS pass...

Posted on your blog.

Steve

This appears to be a problem with SSIS not using escape characters as other parts of the Windows Universe. Any one agree?

It is certainly a resonable option, but there are 65 tables involved and a number of SPs (in the hundreds) that would need the change to piont two different databases....

here is the suggest on MS Connect.

https://connect.microsoft.com/SQLServer/feedback/details/636649/using-the-set-command-to-disable-triggers-during-a-session-without-affecting-any-other-sessions

Being DBA, I don't have control over the code and our developers and already rejected that method. Thanks.

Steve

Will do today. Thanks for that suggetion.

Steve

I agree, we are DBAs though and I will have to get development to do it Meanwhile we are looking into the BULK INSERT using an exported files....

Nope there is too much activity and blocking anyone will not fly.

Yeah we thought of that but we were trying not to modif code. There are about 20 of them on various tables.

Sorry its not sa. It is another user id that has SYSADMIN rights.

It is an old app and the main user id that connects is sysadmin (I know bad design).

Well we tried the single user mode. We are using Lite Speed and it tries to open another connects and fails. So we abandon that method.

Steve

I'll take that as a no there is no direct way. I will investigate the triggers. I am being told they are rather complex.