152 reputation
217
bio website stackoverflow.com
location Canada
age 25
visits member for 1 year, 11 months
seen Dec 23 at 19:03

Dec
12
accepted XACT_ABORT OFF vs COMMIT in trigger
Dec
12
comment XACT_ABORT OFF vs COMMIT in trigger
I've done the test, and it worked - I just want to make sure I understand what I'm doing. I already had the try/catch in there. Thanks for your help!
Dec
12
comment XACT_ABORT OFF vs COMMIT in trigger
Okay, so, just so I understand: COMMIT TRAN ensures the data gets committed (obviously), BEGIN TRAN prevents an error from being thrown, and XACT_ABORT makes the batch succeed despite any errors?
Dec
12
comment XACT_ABORT OFF vs COMMIT in trigger
Well, I'm not getting any error message. What is the point of XACT_ABORT in this situation if I'm already doing a commit?
Dec
12
comment XACT_ABORT OFF vs COMMIT in trigger
@MartinSmith I'm already using service broker.
Dec
12
asked XACT_ABORT OFF vs COMMIT in trigger
Nov
17
comment Localization: One table or multiple tables? (MySQL)
I would store as ID | culture | message instead.
Oct
24
revised Issues with module signing and SSIS catalog internal procedures
added 97 characters in body
Oct
24
accepted Issues with module signing and SSIS catalog internal procedures
Oct
24
comment Issues with module signing and SSIS catalog internal procedures
It already had connect, I think. Anyway, I granted that, still no dice. It seems as though the impersonation/certificate is just being ignored....If I add the restricted account to the ssisdb databases then it gives me errors about the permissions on the individual procs.
Oct
24
comment Issues with module signing and SSIS catalog internal procedures
Thanks for all your help. I granted the appropriate permissions, but I'm still getting the following error:Msg 916, Level 14, State 1, Procedure get_user_info, Line 2 The server principal "RestrictedAccount" is not able to access the database "SSISDB" under the current security context.
Oct
24
comment Issues with module signing and SSIS catalog internal procedures
I tried what you recommended (removing the execute as), yet the impersonation doesn't do anything (I get errors related to the permissions on my restricted account). I'm going to try the SQLCLR option now.
Oct
23
awarded  Notable Question
Oct
22
comment Issues with module signing and SSIS catalog internal procedures
I've checked the owner (it's SA). I'm not sure I understand the revert message: the proc is in MSDB, and the user executing connects to the MSDB databases. I'm not explicitly calling REVERT anywhere. Is the problem with calling the procedures in the SSISDB databases from inside the proc?
Oct
21
comment Issues with module signing and SSIS catalog internal procedures
Thanks for adding the new info. I've verified none of the things are the issue (Except for #1 I am trying to impersonate a service account - not sure if that still applies). I've added more detail to the question.
Oct
21
revised Issues with module signing and SSIS catalog internal procedures
added 1306 characters in body; edited title
Oct
17
comment Issues with module signing and SSIS catalog internal procedures
I have signed the proc in MSDB as well.I receive the same error message when I call the procedure.
Oct
17
comment Issues with module signing and SSIS catalog internal procedures
@RLF No, my procedure lives in the msdb database. I'm calling the internal SSIS Catalog procedures to run the package.
Oct
17
asked Issues with module signing and SSIS catalog internal procedures
Oct
9
accepted Execute permission denied on object sp_start_job