Ask a questionAsk a question
 

QuestionSSIS 2005 Production support

  • Saturday, November 07, 2009 6:06 AMJames1411 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Currently I have been switched to production support for SSIS packages.
    Can anyone provide me the best practices for production support for SSIS 2005 packages.

    So far following are my task:
    Schedule SSIS packages on Sqlserver agent.
    Keep log of pakages and email if any package fail
    check package configuration

    Are there any standard procedure to follow for production  support of SSIS packages.

    Thanks
    I will really appreciate you sugessions.


All Replies

  • Saturday, November 07, 2009 6:40 AMBharani 3010 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi James,
    If you ask me i would say the first two tasks can be automated using SSIS and Jobs itself,
    1. Schedule SSIS packages on Sqlserver agent - Feature available as part of SQL Agent job
    2. Keep log of pakages and email if any package fail -  Logging can be done for packages and send mail tasks can be used inside the package to send mail in either case of failure and success.


    3. Configuration can me  needs to be manually verified before each an every execution.



    Thanks, Bharani M - Please mark the post as answered if it answers your question. - Please vote the post as Helpful if you find the post as helpful.
  • Saturday, November 07, 2009 9:02 AMJames1411 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanks Bharani...
    I also manually change the server names in package configuration for my packages...they are coming from QA server.

    Actually I am looking for any standard  procedure I need to follow for Production support of SSIS packages...like most of DBA's follows for their task.
    Any article link is highly appreciated.

    thanks