Microsoft KB Archive/247052

= FIX: DTS Package Creator/Owner Name Does Not Change When Another User Saves a New Package =

Article ID: 247052

Article Last Modified on 3/14/2006

-

APPLIES TO


 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q247052



BUG #: 55363 (SQLBUG_70)



SYMPTOMS
If one user creates and saves a Data Transformation Services (DTS) package and then later another user edits the package and uses Save As to save the changes into a new package, that new package still has the previous user's name as the Creator in the Package Properties dialog box and as the Owner in the Packages window in SQL Server Enterprise Manager (SEM). However, the Package GUID (globally unique ID) is changed as expected.

Also, when creating and saving a package, the name that is listed as the Creator is the Windows NT user who logged on to the computer, regardless of whether you are using Windows NT Authentication or SQL Server Authentication.



WORKAROUND
To work around this problem, do either of the following:
 * Create a new package from scratch rather than modifying an existing package and using Save As.

-or-
 * Try to ensure that the original package creator makes the necessary changes and then saves the package using Save As.



STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0

For more information, contact your primary support provider.



Steps to Reproduce the Problem
 Create two new Windows NT users. Grant these new users rights to the Pubs and Northwind databases. Log on to Windows NT as one of the new users. In SQL Server Enterprise Manager, create a new DTS package and save it by doing the following:  Under Data Transformation Services in Enterprise Manager, right-click Local Packages and then click New Package on the shortcut menu.</li> On the Task menu, click Transfer SQL Server Objects.</li> On the Source tab, select Windows NT Authentication and the pubs database.</li> On the Destination tab, select Windows NT Authentication and the northwind database.</li> On the Transfer tab, click to clear the Transfer All Objects check box and then click Select Objects.</li> Click to check the authors table (indicating a transfer of the authors table from the pubs database to the northwind database) and then click OK.</li> On the Package menu, click Save As.</li> Select Windows NT Authentication and then click OK.</li></ol> </li> Log off Windows and then log back on as the other user you created in Step 1 of this procedure.</li> Under the Data Transformation Services folder in SQL Server Enterprise Manager, click Local Packages and note that the name in the Owner column is the first user (who created the package).</li> Right-click the package and click Design Package on the shortcut menu.</li> On the Package menu, click Properties. Note the name listed as the Creator and the Package GUID then close the DTS Package Properties dialog box.</li> Make a change to the package. You can do the following to make a simple change: <ol style="list-style-type: lower-alpha;"> Right-click the Transfer SQL Server Objects Task icon and click Properties on the shortcut menu.</li> On the Transfer tab, click Select Objects.</li> Click to clear the check box by the authors table and then click to check the titles table. Next, click OK.</li></ol> </li> On the Package menu, click Save As to save the changes. Change the package name to a new name and then click OK.</li> <li>View the package properties again. Because you have made changes and saved a new package as another user, the Creator should have changed, but it will still show the name of the user who originally created the package. However, the Package GUID has indeed changed as expected.</li></ol>

Keywords: kbbug kbfix KB247052

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.