Post reply

SSIS 101: Object Variables, ResultSets, and Foreach Loop Containers

  • September 25, 2008 at 11:43 pm

    #877427

    Thanks very much Andy.... 🙂

  • November 13, 2008 at 8:14 am

    #898118

    The was great into.!!!!!!!!!

    Need a little though. I have doing same thing except I need to add a where clause to SQL in the Excute SQL Task!

    How does that work?

    I tried:

    Select AdjustSQLCode from _ut_PCA_Client_Import_Format_Cycle_Adjust

    WHERE FormatID = @FormatID

    Mapping Paramter:

    Variable Name = User::FormatID Direction = input DataType = Long Parameter Name = 0

  • November 18, 2008 at 3:47 pm

    #900212

    Terrific article, Andy - many, many thanks.

    This got me started with understanding how to shred SQL data using the Object variable type. This understanding will now help me implement all kinds of great functionality at work.

    Thanks again.

    - Simon

  • February 6, 2009 at 3:08 am

    #939360

    i didnt unserstand from where we have to configure the store procedure so that its performance can increase twice from earlier..plz im cinfused..if im calling the store procedure from C# file..how can i do this.i will be realy thankful to u

  • February 6, 2009 at 8:03 am

    #939540

    good article, can't wait to try it Thanks;)

  • February 6, 2009 at 12:39 pm

    #939741

    Hi Rana,

    I'm not sure this article will help you. It was about SSIS and didn't really touch on C#.

    Andy

    Andy Leonard, Chief Data Engineer, Enterprise Data & Analytics

  • February 6, 2009 at 2:37 pm

    #939806

    thank alot for replying.and im really very happy that only today i joind this community,i mean i got registered on this site and i asked question and got reply very soon..sorry i took the topic wrong.actually i read very less ,i was facinated by the line..store procedure calls performance can be increased by twice..

  • February 6, 2009 at 3:57 pm

    #939850

    Nice article, Andy. I tried this on SS2k8 and one thing that surprised me was a number of small details that changed and threw me first: Like "Dts.Results.Success" no longer works and is replaced by "ScriptResults,Success".

    [font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
    Proactive Performance Solutions, Inc.     [/font]    [font="Verdana"] "Performance is our middle name."[/font]

  • February 6, 2009 at 4:24 pm

    #939853

    RBarryYoung (2/6/2009)

    Nice article, Andy. I tried this on SS2k8 and one thing that surprised me was a number of small details that changed and threw me first: Like "Dts.Results.Success" no longer works and is replaced by "ScriptResults,Success".

    Is it really ScriptResults[comma]Success?:D

    Jack Corbett
    Consultant - Straight Path Solutions
    Check out these links on how to get faster and more accurate answers:
    Forum Etiquette: How to post data/code on a forum to get the best help
    Need an Answer? Actually, No ... You Need a Question

  • February 6, 2009 at 5:21 pm

    #939871

    Jack Corbett (2/6/2009)

    RBarryYoung (2/6/2009)

    Nice article, Andy. I tried this on SS2k8 and one thing that surprised me was a number of small details that changed and threw me first: Like "Dts.Results.Success" no longer works and is replaced by "ScriptResults,Success".

    Is it really ScriptResults[comma]Success?:D

    Ooops. Heh, yeah I guess that would be a very surprising change!

    [font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
    Proactive Performance Solutions, Inc.     [/font]    [font="Verdana"] "Performance is our middle name."[/font]

  • February 7, 2009 at 4:48 am

    #939947

    Great article....

  • February 8, 2009 at 4:32 am

    #940134

    Thanks for all the encouragement!

    RBarry, I mostly write about SSIS 2005 because I sense most of the SSIS market is using SSIS 2005. I could be wrong. I plan to switch to writing about SSIS 2008 this year.

    :{> Andy

    Andy Leonard, Chief Data Engineer, Enterprise Data & Analytics

  • February 8, 2009 at 6:35 am

    #940141

    Oh I think that you're right, Andy. I wasn't trying to be critical, I just happened to have the 2008 version open at the time, so I tried it out there. I had initially thought that there would be no code-level difference, but was surprised that there was. I wonder if that breaks when you upgrade or does it convert it?

    [font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
    Proactive Performance Solutions, Inc.     [/font]    [font="Verdana"] "Performance is our middle name."[/font]

  • February 8, 2009 at 7:12 am

    #940147

    Hi RBarry,

    I didn't take it as a criticism - I appreciate the comment.

    In my experience, scripts don't convert well from SSIS 2005 to SSIS 2008. I suspect it has a lot to do with the changes to the script engine. SSIS 2005 uses Visual Studio for Applications (VSA) and SSIS 2008 uses Visual Studio Tools for Applications (VSTA).

    (You probably already know this. I type it for the benefit of those who happen upon this thread while searching...)

    :{> Andy

    Andy Leonard, Chief Data Engineer, Enterprise Data & Analytics

  • February 24, 2009 at 12:17 am

    #949163

    Thanks for the Article. I had been fighting to get the object type into foreachloop for a day. this article saved a lot of time. very well written.

Viewing 15 posts - 16 through 30 (of 63 total)

You must be logged in to reply to this topic. Login to reply