How to Import SSIS Packages into a Clustered SQL Server 2008 environment?

  • Hi All,

    I am new to SQL Server 2008 and SSIS, we have been aked to deploy SSIS packages on to a clustered SQL 2008 Server environment. I am not sure how to deploy the SSIS packages in a clustered SQL server environment. Can i import the SSIS packages to the MSDB in SQL Server Cluster and schedule a SQL Job to run the packages? Since it is a 2 node fail over cluster i am not sure whether to use the import to MSDB or to a file system. If i use a file system then i am not sure where to place the package as the package has to available on both the servers.

    Please advise. I am confused on this.

    Regards,

    Srikant

  • you can run ssis package from a job

    create a new job

    and whan you add a steep to the job

    in the type drop down list select

    sql server integration services package

    and browse the ssis package file

  • Thanks Roi,

    So when i import the package, i should import the package to the SQL Server 2008 Clustered Virtual Name and then Create Jobs to run the packages. For this i think i need to install SSIS locally on both the nodes of my SQL Server FailOver Cluster.

    Please correct me if i am wrong.

  • So when i import the package, i should import the package to the SQL Server 2008 Clustered Virtual Name and then Create Jobs to run the packages. For this i think i need to install SSIS locally on both the nodes of my SQL Server FailOver Cluster.

    SSIS is not cluster aware. We have a similar setup to yours and install SSIS on only one side of the cluster. As you suggest, we deploy packages to the clustered virtual name and then create SQL jobs to run these packages.

    Ken

  • Thanks for the clarifications Ken.

  • you dont need to have the ssis install on non of the 2 computers

    whan you create the steep

    after you select

    sql server integration services package

    in the type drop down list

    and then

    select file system

    on package source drop down list

    and give the file path for your package

    if you dont have it on the server first copy the package to the server

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

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