exec - Risks of using SQL trigger to run an exe -


What are the risks of running an XE on a SQL Trigger? This is a closed server, intranet, only with limited user access to the server where the script runs and the SQL Server connection.

I temporarily store outgoing email in a table in my database system. Then it is sent through a trigger which runs and exe. Draws the topic, CC, and body from the Exchange directly, from the DEB and sends the email through the CDO.

I just have to use an external method of sending the email instead of sending the code back from the back to the website to avoid slwodown I asked about this specific problem in another post, but exec risks Asking about a different issue seemed to direct any of the options for the related post

If this is a closed server and Exe is known, I do not know if there are any more risks. I could see that the only risk would be when someone changed your extension to something that would begin, but it seems like the scenario you described.

Our situation was many years ago, where we had a vendor whose product was updated through a control program. We had a trigger that was added every time the user was added to the SQL database, and the control program would then prompt the user to add their services there. There was never a real problem with it.

Comments

Popular posts from this blog

Python SQLAlchemy:AttributeError: Neither 'Column' object nor 'Comparator' object has an attribute 'schema' -

java - How not to audit a join table and related entities using Hibernate Envers? -

mongodb - CakePHP paginator ignoring order, but only for certain values -