Post reply

Can i change Provider in package by Execute Package Utility

  • February 21, 2011 at 5:09 am

    #388905

    Hi,

    I have created a package using Provider SQLCLI but it executed successfully in Dev & Test environments.

    But its failed in UAT due to the non existance of SQLCLI it has SQLCLI10.

    Can i change the Provider of package as follows to get succeded in Job execution.

    Execute Package Utility->Connection Managers->Check the Box -> Update the provider to latest -> Click on Execute

    Any easy way to get succeded the Job itself without opning in BIDS.

  • February 21, 2011 at 7:36 am

    #1289419

    You can't directly update your providers.

    You can however configure your connection managers with package configurations, and you should, as it is a best practice.

    The package configurations in the UAT environment will contain the right providers.

    I'm guessing you created the package on BIDS 2005 and that the UAT server is SQL Server 2008, so you should also check if there aren't any other issues by letting an older package run on a newer server.

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

  • February 22, 2011 at 12:49 am

    #1289716

    Thanks for Info...

    I developed in BIDS 2005. BUt the UAT & Production are 2008.

    I did the changes by open the Package with notepad and replaced the SQLNCLI.1 Provider with SQLNCLI10, It worked.

    Is there Any issues in the future if i did like this?

    Thanks,

    Sasidhar Pulivarthi

  • February 22, 2011 at 1:14 am

    #1289726

    Yes, if you have a large production environment with over 100+ packages, good luck with opening them with notepad to change the provider, every time you want to deploy them.

    You should look into package configurations.

    Furthermore, developing on another version as the one on the server could get you into trouble with deprecated features. OK, there aren't that many between 2005 and 2008, so you're quite OK. (just to give some examples: the names of internal tables in msdb have changed and also the name of the default logging table of SSIS)

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

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

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