Connection string properties in a trigger

Question

question

Marc asked Jan 28, '10

Connection string properties in a trigger

I have written a trigger that requires information that does not exist in the table being updated. I thought that if I could examine the properties in the connection string that was used to update the table, I could communicate the information to the trigger.

I have examined various system functions to no avail. I hope someone can shed some light on my problem.

trigger connection-string meta-data

2

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Matt Whitfield ♦♦ commented · Jan 28, 2010 at 08:52 PM

When you say 'does exist' do you mean 'does not exist'? What is the information, what are you trying to do?

0 ·

Marc commented · Jan 28, 2010 at 08:54 PM

Yes, I just fixed my post. Thanks.

0 ·

Answer 1 · 2010-01-28T17:21:50Z

David 1 answered Jan 28, '10

Why can't you pass this information as a parameter to a regular stored proc? Stored procedures can have parameters. Triggered procedures cannot.

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 2 · 2010-01-28T22:01:54Z

Rob Farley answered Jan 28, '10

Some are available, most significantly, APP_NAME(), and SYSTEM_USER. I guess it depends on what you're looking for.

1

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Marc commented · Jan 29, 2010 at 02:36 PM

I would like to put a value into the connection string, execute the update and have the value available to the trigger when it executes.

0 ·

question