![]() ![]() Although I prefer making the initial change in the package itself before creating the config file. As we know, the values in the config file override the design time values when the package is running. Edit the Connection String property to change the Application Name parameter of the connection in this window.Įdit the Connection String property to change the Application Name parameter of the connection in the config file. Right click the OLEDB connection and select Properties (or select the connection and press F4). This can be fixed easily with any one of the following methods. ![]() Anyone monitoring the Production server with a SP_WHO2 would see a package running with a funny long name including GUID and the development server name. At the time of migrating the package and its config file to the QA and Production environment, the developers usually change the Data Source and Initial Catalog in the connection string but leave the Application Name as it is. When the developers create the packages on a development server, the connection string includes the development server name. This application name will be exported out to the config file too. Also, this is what you will see in the Program Name column of SP_WHO2 results when the package is running. It has the name of the package, a unique Id for the connection, the SQL server name and the database name. ![]() Notice the Application Name parameter in bold font. The default connection string for a OLEDB connection looks something like this – Data Source=(local) Initial Catalog=ReportServer Provider=SQLNCLI10.1 Integrated Security=SSPI Auto Translate=False Application Name=SSIS-DemoOLEDBPackage-(local).ReportServer ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |