You've already identified that this is unsupported. I would also worry about the performance implications of running an SSIS package via a trigger.
Instead, I'd use a different mechanism to run the process, which is fully supported:
- Still use an SSIS package
- Create a custom entity in CRM - let's call it triggerPackage
- Create a workflow on the data operation(s) that should send data. In that workflow create a triggerPackage record
- Add a step in the SSIS package to check for any active triggerPackage records. If there are, then create the XML, and as a final step, deactivate the active triggerPackage record(s)
- Run the SSIS package via a SqlAgent job that runs on a schedule - maybe every 5 minutes
You won't find any OOTB solution to send xml data, as you'd need to specify what data to send, and how to structure it. As you're already using SQL, I'd use a FOR XML clause on the SELECT statement to generate the XML, which you can then write to a file
and send via FTP within SSIS.
Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk
