Scenario:
Legacy App/DB using Sql 2K, but for all intents and purposes it's dBase on Sql Server.
We do not have access to the application code base. Or an API to hook into the code base.
There are few, if any data validation checks in the system.
Our Solution:
Append trigger(s) to specific table(s) to audit information. If information is invalid send an email to specific user(s).
I have everything up and running in my sandbox. Running through the different test scenarios I encountered 1 final problem which I can't remedy. 99% of our users can't access master.dbo.xp_sendmail.
Is there a way to "run as"? Or another way to send mail which the common end user can execute?
Jason Meckley
Programmer
Specialty Bakers, Inc.
Legacy App/DB using Sql 2K, but for all intents and purposes it's dBase on Sql Server.
We do not have access to the application code base. Or an API to hook into the code base.
There are few, if any data validation checks in the system.
Our Solution:
Append trigger(s) to specific table(s) to audit information. If information is invalid send an email to specific user(s).
I have everything up and running in my sandbox. Running through the different test scenarios I encountered 1 final problem which I can't remedy. 99% of our users can't access master.dbo.xp_sendmail.
Is there a way to "run as"? Or another way to send mail which the common end user can execute?
Jason Meckley
Programmer
Specialty Bakers, Inc.