FIX: DTS Transfer Objects May Fail if Dependent Objects Are Not in Alphabetical Order (291780)

The information in this article applies to:

Microsoft SQL Server 2000 (all editions)

This article was previously published under Q291780

BUG #: 351620 (SHILOH_BUGS)

SYMPTOMS

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

CAUSE

The objects are scripted out in alphabetical order; therefore, not all dependent objects may have been created.

RESOLUTION

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 the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack

WORKAROUND

To work around this problem, enable the Include Dependent Objects property.

STATUS

Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.

MORE INFORMATION

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]
GO

CREATE VIEW E_Main_View
AS
SELECT *
FROM [dbo].[New_Table]
GO

CREATE VIEW D_Dependent_View
AS
SELECT [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.

Modification Type:	Major	Last Reviewed:	11/6/2003
Keywords:	kbBug kbfix kbSQLServ2000sp1fix KB291780