November 10, 2009 at 4:53 am
Nop still don't understand, perhaps I'm having a blonde day!
The output shows....
TCP TSQL SQL
COMWTSV06 DATA_LOAD DATA_LOAD
DATA_LOAD being the local user login....
Listen don't worry, it's working for me I was just trying to help the original poster......
Peter Gadsby
Business Intelligence Consultant
www.hgconsult.co.uk
November 10, 2009 at 5:04 am
I meant the output might help explain it to me! 😀
It didn't. I suppose your SQL Server team might have hacked sp_send_dbmail - the default procedure has an EXECUTE AS 'dbo' on the procedure, but an EXECUTE AS CALLER wrapped around the bit that attaches the file.
I wonder if they have changed that to EXECUTE AS SELF/OWNER/a user mapped to a windows login and removed the EXECUTE AS CALLER bit...? Wouldn't be supported, but it's an interesting idea. I might try it later just to see.
Paul
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
November 10, 2009 at 5:07 am
Nothing has changed to the SP they are using the standard one.
Peter Gadsby
Business Intelligence Consultant
www.hgconsult.co.uk
November 11, 2009 at 4:55 pm
Paul,
How I can vinculate a SQL Server account to Windows account?
Thanks by your help,
January 8, 2013 at 7:56 pm
Try to use SA account as a Test
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply