No, it’s not possible, you’re dreaming. Or is it? Well, sort of. What’s possible is the following:
- I have created an entity called “new_pluginlauncher”. I have made a plugin firef upon the creation of a record of this entity, from which I can do anything, depending on the parameters passed when creating the record. I can do things such as win or reopen a quote, create an order, close a case, well whatever really. As long as the correct guids and parameters are set upon record creation.
- I have created an SSIS package, based on Kingswaysoft, that does that: create a record of that new_pluginlauncher entity
- I have deployed the SSIS package appropriately in the SQL Server instance
- I have created a stored procedure that calls that SSIS package
Bingo! From now on, I can access plugin code, on demand, from a SQL Server stored procedure.
And the best thing is: this is completely supported.
Here’s the code of the stored procedure. Pay attention to allowing xp_cmdshell.