﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Integration Services / Data Warehousing  / Calling SSIS Package in a trigger / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Thu, 20 Jun 2013 04:45:51 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Calling SSIS Package in a trigger</title><link>http://www.sqlservercentral.com/Forums/Topic1405226-364-1.aspx</link><description>If all you are doing is copying the data from one instance to another, then I would agree that replication is probably a far better solution.  It sounds to me as if you are trying to develop something that is already built in.  :-D</description><pubDate>Fri, 11 Jan 2013 12:20:48 GMT</pubDate><dc:creator>Bruce W Cassidy</dc:creator></item><item><title>RE: Calling SSIS Package in a trigger</title><link>http://www.sqlservercentral.com/Forums/Topic1405226-364-1.aspx</link><description>[quote][b]mpradeep23 (1/10/2013)[/b][hr]CDC works if tables are in different instances of sql sever?thank spradeep[/quote]Sure, CDC is an option but if you do not need a record of all historical data changes then it is likely overkill and still will not deliver real-time data to the downstream system. With CDC changes are queued on the source system. You'll still need a process to take those changes and push them to a downstream system which is likely going to best implemented as an SSIS package. Most types of SQL Server Replication require no development, only configuration. Have you looked into? I think you would be interested in Transactional Replication with a Push Subscription from your upstream system to your downstream system which requires no development and delivers as close to real-time data on the subscriber as possible.</description><pubDate>Thu, 10 Jan 2013 06:39:48 GMT</pubDate><dc:creator>opc.three</dc:creator></item><item><title>RE: Calling SSIS Package in a trigger</title><link>http://www.sqlservercentral.com/Forums/Topic1405226-364-1.aspx</link><description>What about setting up replication for the table(s) in question?</description><pubDate>Thu, 10 Jan 2013 04:31:47 GMT</pubDate><dc:creator>anthony.green</dc:creator></item><item><title>RE: Calling SSIS Package in a trigger</title><link>http://www.sqlservercentral.com/Forums/Topic1405226-364-1.aspx</link><description>CDC works if tables are in different instances of sql sever?thank spradeep</description><pubDate>Thu, 10 Jan 2013 04:17:31 GMT</pubDate><dc:creator>mpradeep23</dc:creator></item><item><title>RE: Calling SSIS Package in a trigger</title><link>http://www.sqlservercentral.com/Forums/Topic1405226-364-1.aspx</link><description>[quote][b]mpradeep23 (1/10/2013)[/b][hr]i have two tables in two sql servers i need two move data from one table to other on insert /update i had written a ssis package for this so when thier is update in one table then i need update it in to other table so for that can i call SSIS Package in Trigger so that will copy the data from source to destination thanks pradeep[/quote]Imagine a process on server 1 which has been written by a C# guy who knows nothing about set-based programming. He is inserting 10,000 rows one at a time in a loop in his program. Do you really want a trigger to execute an SSIS package 10,000 times in just a few seconds? Far better to run the package every few minutes &amp; pick up any changes then. Or use CDC if you have a high enough version of SQL Server.</description><pubDate>Thu, 10 Jan 2013 02:28:05 GMT</pubDate><dc:creator>Phil Parkin</dc:creator></item><item><title>RE: Calling SSIS Package in a trigger</title><link>http://www.sqlservercentral.com/Forums/Topic1405226-364-1.aspx</link><description>i have two tables in two sql servers i need two move data from one table to other on insert /update i had written a ssis package for this so when thier is update in one table then i need update it in to other table so for that can i call SSIS Package in Trigger so that will copy the data from source to destination thanks pradeep</description><pubDate>Thu, 10 Jan 2013 01:54:54 GMT</pubDate><dc:creator>mpradeep23</dc:creator></item><item><title>RE: Calling SSIS Package in a trigger</title><link>http://www.sqlservercentral.com/Forums/Topic1405226-364-1.aspx</link><description>[quote][b]mpradeep23 (1/10/2013)[/b][hr]Hi i trying call SSIS Package from a Trigger is there any  perforamnce issue to the databasethanks in advance with best regardspradeep[/quote]Based on the limited information provided, my best answer is 'probably' and my advice would be to look for an alternative solution to whatever requirement you have been given.</description><pubDate>Thu, 10 Jan 2013 01:43:12 GMT</pubDate><dc:creator>Phil Parkin</dc:creator></item><item><title>Calling SSIS Package in a trigger</title><link>http://www.sqlservercentral.com/Forums/Topic1405226-364-1.aspx</link><description>Hi i trying call SSIS Package from a Trigger is there any  perforamnce issue to the databasethanks in advance with best regardspradeep</description><pubDate>Thu, 10 Jan 2013 00:03:03 GMT</pubDate><dc:creator>mpradeep23</dc:creator></item></channel></rss>