FIX: DTS Transfer Objects May Fail if Dependent Objects Are Not in Alphabetical Order
This article was previously published under Q291780
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 351620 (SHILOH_BUGS)
The DTS Transfer Manager may fail to transfer all objects if the dependencies do not occur in alphabetical order and you attempt to copy specific objects.
The DTS package reports the following message:
Invalid Object Name
The objects are scripted out in alphabetical order; therefore, not all dependent objects may have been created.
To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
INF: How to Obtain the Latest SQL Server 2000 Service Pack
To work around this problem, enable the Include Dependent Objects property.
Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.
To reproduce the problem, you can use the following script as an example:
CREATE TABLE [dbo].[New_Table] ( [Name] [char] (10) COLLATE SQL_Latin1_General_CP1_CI_AS NULL , [Age] [decimal](18, 0) NULL ,) ON [PRIMARY]GOCREATE VIEW E_Main_ViewASSELECT *FROM [dbo].[New_Table]GOCREATE VIEW D_Dependent_ViewASSELECT [Name] FROM [dbo].[E_Main_View]
During the transfer, if you select to transfer all three objects, DTS fails when trying to transfer D_Dependent_View, with the following message:
Invalid Object Name 'dbo.E_Main_View'
The failure occurs because E_Main_View has not been transferred.
Article ID: 291780 - Last Review: 01/16/2015 21:55:35 - Revision: 3.2
- Microsoft SQL Server 2000 Standard Edition
- kbnosurvey kbarchive kbbug kbfix kbsqlserv2000sp1fix KB291780