<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
»
Article Discussions
»
Article Discussions by Author
»
Discuss content posted by Stan Kulp
»
A script task alternative to a massive SSIS...
A script task alternative to a massive SSIS multicast transformation
Rate Topic
Display Mode
Topic Options
Author
Message
Stan Kulp-439977
Stan Kulp-439977
Posted Monday, January 16, 2012 10:42 PM
SSC Journeyman
Group: General Forum Members
Last Login: Yesterday @ 2:08 PM
Points: 79,
Visits: 600
Comments posted to this topic are about the item
A script task alternative to a massive SSIS multicast transformation
Post #1236984
Samuel Vella
Samuel Vella
Posted Tuesday, January 17, 2012 9:00 AM
Old Hand
Group: General Forum Members
Last Login: Today @ 3:04 AM
Points: 328,
Visits: 1,849
Hi Stan, nice article, however I can't really see this as a replacement for the multicast problem mentioned, as that is a problem which should never exist in the first place.
What it does look like a potentially robust replacement for is the File System task as this would be able to wrap up some of does file checking logic and keep it out of the Control Flow area.
Should mention that error handling using a message box should only be used in a demonstation scenario. If this was a scheduled package which behaved like this then it would stop processing as it waited for the phantom desktop user to click OK!
Post #1237288
Obs
Obs
Posted Tuesday, January 17, 2012 9:37 AM
SSC Veteran
Group: General Forum Members
Last Login: Friday, April 05, 2013 2:29 PM
Points: 247,
Visits: 392
I'm not a fan of this. Aside from it being a maintenance issue (editing the SSIS package every time a new folder is needed or removed), you could at least use a for each task and iterate over a list of directories. Inside of that loop, you could use expressions within a file task to copy it around.
Post #1237326
Stan Kulp-439977
Stan Kulp-439977
Posted Tuesday, January 17, 2012 10:00 AM
SSC Journeyman
Group: General Forum Members
Last Login: Yesterday @ 2:08 PM
Points: 79,
Visits: 600
To be honest, the only reason I wrote this is because somebody responding to one of my previous articles asked how it could be done.
Just because something can be done doesn't mean it should be done, but sometimes it's fun to do it anyway.
Post #1237350
Obs
Obs
Posted Tuesday, January 17, 2012 10:42 AM
SSC Veteran
Group: General Forum Members
Last Login: Friday, April 05, 2013 2:29 PM
Points: 247,
Visits: 392
Fair enough. I feel the same way about Powershell.
Post #1237380
Charles Kincaid
Charles Kincaid
Posted Tuesday, January 17, 2012 12:16 PM
Right there with Babe
Group: General Forum Members
Last Login: Friday, May 17, 2013 9:18 AM
Points: 772,
Visits: 1,825
Obs (1/17/2012)
I'm not a fan of this. Aside from it being a maintenance issue (editing the SSIS package every time a new folder is needed or removed), you could at least use a for each task and iterate over a list of directories. Inside of that loop, you could use expressions within a file task to copy it around.
It's still good as a teaching exercise. In practice it might be better to have a scratch location for the master and then read the destinations from some table. If you are going in for the script task (VB or C#) then take a closer look into the File I/O objects. I seem to remember that you can specify overwrite or not.
ATB
Charles Kincaid
Post #1237433
MWise
MWise
Posted Tuesday, January 17, 2012 1:03 PM
Old Hand
Group: General Forum Members
Last Login: Monday, May 20, 2013 9:31 AM
Points: 381,
Visits: 1,481
I'd definitely go with a For Each Loop and use the File Copy Task. I'd either read from a database table or configuration file. That way you don't have to touch the SSIS package when you have to change the copy locations. Honestly, I hate having tasks buried in code when there are already SSIS components available to use. I find having to crack open the code editor a PITA, and even more annoying when the developer doesn't include comments on what the code is doing and why.
Mwise
Post #1237466
Obs
Obs
Posted Tuesday, January 17, 2012 1:19 PM
SSC Veteran
Group: General Forum Members
Last Login: Friday, April 05, 2013 2:29 PM
Points: 247,
Visits: 392
Charles Kincaid (1/17/2012)
It's still good as a teaching exercise. In practice it might be better to have a scratch location for the master and then read the destinations from some table. If you are going in for the script task (VB or C#) then take a closer look into the File I/O objects. I seem to remember that you can specify overwrite or not.
Perhaps as a "How to make this better" exercise
Post #1237482
SQLRNNR
SQLRNNR
Posted Tuesday, January 17, 2012 2:47 PM
SSCoach
Group: General Forum Members
Last Login: Monday, May 20, 2013 1:07 PM
Points: 18,733,
Visits: 12,332
Charles Kincaid (1/17/2012)
...In practice it might be better to have a scratch location for the master and then read the destinations from some table.
I like this idea. While reading the article, this is what stood out to me as an obvious way to improve on the package.
Jason
AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server 2008
SQL RNNR
Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #1237548
sharath.chalamgari
sharath.chalamgari
Posted Wednesday, January 18, 2012 2:04 AM
Ten Centuries
Group: General Forum Members
Last Login: Monday, September 17, 2012 7:30 AM
Points: 1,038,
Visits: 679
nice article, How about just writing a file to the single location and then use a batch job to copy it to the diffrent folders where ever you want. may be we can include this in another step of the job that we call the ssis package.
Post #1237749
« Prev Topic
|
Next Topic »
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.
