Post reply

What are the ScriptingLanguages which can be supported by SSIS (2008 +)?

  • September 20, 2013 at 11:42 am

    #278213

    I know that it supports MS Visual C# and Visual Basic. Can we add more languages to it ? For example - Python, Java, JavaScript etc. ?

    Also, I have a career related question - If those are the only 2 languages, then is it a must to have "advanced" skills in both as opposed to "beginner" or "intermediate" skills ? Do real SSIS developers need to use these languages often in their script tasks ?

    Thanks.

  • September 20, 2013 at 12:08 pm

    #1652000

    etl.laptop (9/20/2013)

    I know that it supports MS Visual C# and Visual Basic. Can we add more languages to it ? For example - Python, Java, JavaScript etc. ?

    Also, I have a career related question - If those are the only 2 languages, then is it a must to have "advanced" skills in both as opposed to "beginner" or "intermediate" skills ? Do real SSIS developers need to use these languages often in their script tasks ?

    Thanks.

    In a Script Task, you've got VB.NET and C# - that's it. Most companies use one or the other (not both) with C# being slightly more common in my experience. I would not say that advanced skills are needed, intermediate is fine. You're not designing a massive multi-form application here - usually just moving data and files around and manipulating properties and variables.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • September 20, 2013 at 3:22 pm

    #1652061

    Thanks. Your answer makes sense to me.

  • September 20, 2013 at 5:28 pm

    #1652088

    Phil Parkin (9/20/2013)

    etl.laptop (9/20/2013)

    I know that it supports MS Visual C# and Visual Basic. Can we add more languages to it ? For example - Python, Java, JavaScript etc. ?

    Also, I have a career related question - If those are the only 2 languages, then is it a must to have "advanced" skills in both as opposed to "beginner" or "intermediate" skills ? Do real SSIS developers need to use these languages often in their script tasks ?

    Thanks.

    In a Script Task, you've got VB.NET and C# - that's it. Most companies use one or the other (not both) with C# being slightly more common in my experience. I would not say that advanced skills are needed, intermediate is fine. You're not designing a massive multi-form application here - usually just moving data and files around and manipulating properties and variables.

    Is there a list of "common jobs which can be done ONLY by Script" ? Eg. Check if a file exists or not etc. ?

  • September 21, 2013 at 12:00 am

    #1652112

    etl.laptop (9/20/2013)

    Phil Parkin (9/20/2013)

    etl.laptop (9/20/2013)

    I know that it supports MS Visual C# and Visual Basic. Can we add more languages to it ? For example - Python, Java, JavaScript etc. ?

    Also, I have a career related question - If those are the only 2 languages, then is it a must to have "advanced" skills in both as opposed to "beginner" or "intermediate" skills ? Do real SSIS developers need to use these languages often in their script tasks ?

    Thanks.

    In a Script Task, you've got VB.NET and C# - that's it. Most companies use one or the other (not both) with C# being slightly more common in my experience. I would not say that advanced skills are needed, intermediate is fine. You're not designing a massive multi-form application here - usually just moving data and files around and manipulating properties and variables.

    Is there a list of "common jobs which can be done ONLY by Script" ? Eg. Check if a file exists or not etc. ?

    I can make one up - at least from my point of view. Others will no doubt have their own input.

    Here are a few script task jobs:

    1) File moving, copying and renaming. The File System Task does it, but it's so much easier to do this in a script task.

    2) Setting the values of package variables.

    3) Altering connection properties at run time - for dynamic connections.

    4) Debugging (eg, displaying a MessageBox to check things as the package runs). Don't leave this stuff in production code though.

    Common ETL tasks can usually be handled without scripting. The script task is there to support you when you want to do something special (eg, I saw a question not very long ago asking whether the script task could be used to concatenate two TIFF files (yes)).

    Interestingly, your example can generally be done without a script task. Just create a foreach container and set your file spec appropriately - then whatever is inside the container will be executed only when that file exists.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

Viewing 5 posts - 1 through 4 (of 4 total)

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