<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2008
»
T-SQL (SS2K8)
»
SSIS Package Inside Trigger keeps running...
16 posts, Page 2 of 2
««
1
2
SSIS Package Inside Trigger keeps running endlessly
Rate Topic
Display Mode
Topic Options
Author
Message
vinu512
vinu512
Posted Thursday, October 18, 2012 6:57 AM
Ten Centuries
Group: General Forum Members
Last Login: Yesterday @ 12:37 AM
Points: 1,047,
Visits: 1,439
Eugene Elutin (10/18/2012)
Did your "above you" insisted that you should use trigger to execute XP_CMDSHELL? Or they just told you that SSIS should start as soon as records inserted?
I would not definitely, under any circumstances, call xp_cmdsheel from a trigger - just NEVER.
You may try to create scheduled task and use msdb.dbo.sp_start_job to start it from the trigger, that may be a bit better...
Also you can use Service Broker.
Hi Eugene,
The "above me" above me asked me to call the SSIS package from a Trigger without making the package a part of a job. So I was pretty much left with Xp_cmdshell. Any other suggestions of doing it are very welcome. Thanks for ur time.
Vinu Vijayan
For better and faster solutions please check...
"How to post data/code on a forum to get the best help" - Jeff Moden
Post #1374313
GSquared
GSquared
Posted Thursday, October 18, 2012 7:01 AM
SSCoach
Group: General Forum Members
Last Login: Monday, May 06, 2013 1:09 PM
Points: 15,439,
Visits: 9,569
vinu512 (10/18/2012)
Eugene Elutin (10/18/2012)
Did your "above you" insisted that you should use trigger to execute XP_CMDSHELL? Or they just told you that SSIS should start as soon as records inserted?
I would not definitely, under any circumstances, call xp_cmdsheel from a trigger - just NEVER.
You may try to create scheduled task and use msdb.dbo.sp_start_job to start it from the trigger, that may be a bit better...
Also you can use Service Broker.
Hi Eugene,
The "above me" above me asked me to call the SSIS package from a Trigger without making the package a part of a job. So I was pretty much left with Xp_cmdshell. Any other suggestions of doing it are very welcome. Thanks for ur time.
You could do a CLR trigger, if the server/database allows that. It's an option, but I don't know that it's actually any better.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Post #1374315
vinu512
vinu512
Posted Friday, October 19, 2012 3:12 AM
Ten Centuries
Group: General Forum Members
Last Login: Yesterday @ 12:37 AM
Points: 1,047,
Visits: 1,439
I really don't know a lot about CLR. And I think if I start now then it would be really time consuming. So, I'd rather stick to solving this problem the way it is for right now. I'll give CLR Triggers some time after I'm finished with the task at hand.
So, please guys.....any other suggestions of how I could get this to work??
Vinu Vijayan
For better and faster solutions please check...
"How to post data/code on a forum to get the best help" - Jeff Moden
Post #1374698
GSquared
GSquared
Posted Wednesday, October 24, 2012 7:22 AM
SSCoach
Group: General Forum Members
Last Login: Monday, May 06, 2013 1:09 PM
Points: 15,439,
Visits: 9,569
vinu512 (10/19/2012)
I really don't know a lot about CLR. And I think if I start now then it would be really time consuming. So, I'd rather stick to solving this problem the way it is for right now. I'll give CLR Triggers some time after I'm finished with the task at hand.
So, please guys.....any other suggestions of how I could get this to work??
Add logging to the SSIS package. See where it gets to, or if it even starts, when fired from the trigger. When you find that out, you'll have a better idea of what needs to be fixed/modified.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Post #1376458
vinu512
vinu512
Posted Thursday, October 25, 2012 10:17 PM
Ten Centuries
Group: General Forum Members
Last Login: Yesterday @ 12:37 AM
Points: 1,047,
Visits: 1,439
Thanks GSquared......I'll add logging and trace the package. I'll get back to you on this one after I'm done with it.
Vinu Vijayan
For better and faster solutions please check...
"How to post data/code on a forum to get the best help" - Jeff Moden
Post #1377384
Bhuvnesh
Bhuvnesh
Posted Friday, October 26, 2012 9:21 AM
SSCrazy
Group: General Forum Members
Last Login: Tuesday, March 26, 2013 8:41 AM
Points: 2,562,
Visits: 3,451
vinu512 (10/19/2012)
So, please guys.....any other suggestions of how I could get this to work??
for the time begin you can test the SSIS package manually . see if it get blocking only by trigger call or not ? additionally i will say if you can make the ssis's stuff asynchrous then try to use service broker. SSIS call within the trigger will be cumbersome sooner or later you need to change this approach
-------Bhuvnesh----------
While 1 = 1 (Learning SQL....)
Click to get fast response of your post
Post #1377674
« Prev Topic
|
Next Topic »
16 posts, Page 2 of 2
««
1
2
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
