SSIS 2005 Deployment

  • I am considering deployment my SSIS package to SQL Server instead of the file system.

    Is msdb the only database that you can deploy the package to?

    What are the advantages of using the database instead of the file system?

    I have a configuration table on another database (not msdb). Would that cause a problem?

    We use Control-M to schedule the running of different items. Can Control-M Work with an SSIS package stored on the server?

  • imani_technology (6/20/2010)


    What are the advantages of using the database instead of the file system?

    I can answer this question. The advantages are that you can use built-in features of SQL Servers, such as security and versioning.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • imani_technology (6/20/2010)


    I have a configuration table on another database (not msdb). Would that cause a problem?

    I can answer this...

    Configuration table can be any where, any data base. Connection to the configuration table can be defined in any XML file or Environment Variable

    ------------------
    Why not ?

  • imani_technology (6/20/2010)


    I am considering deployment my SSIS package to SQL Server instead of the file system.

    Is msdb the only database that you can deploy the package to?

    Yes.

    See article

    http://msdn.microsoft.com/en-us/library/ms137916.aspx

  • Control-M is a scheduler and it cannot schedule the job deployed in SQL Server.

    You can use the SQL agent to do the job.

    I would suggest you to deploy it on file system for the control-m to schedule it.

    I recommend http://www.expertmsbitraining.com

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

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