BUG: Trans Mgr Gives Errors When St Proc Has Only 1 Dependency

 Last reviewed: May 2, 1997
Article ID: Q142759

The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG# NT: 12786 (4.21a)

SYMPTOMS

Using Transfer Manager to transfer a stored procedure which has only one dependency can fail.

WORKAROUND

You can generate scripts for procedures using SQL Enterprise Manager or Object Manager and run them in the destination database.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

  1. Assume a stores procedure C references two tables, A and B. If you try to transfer the procedure to a new database with INCLUDE DEPENDENCIES and INCLUDE DROPS (with or without INCLUDE DATA), the transfer completes successfully.

  2. If procedure C references only one table, say A, then the transfer fails. The error is "invalid object A."

  3. Even if C references A, and A has a trigger A_trig, the transfer fails.

So to conclude, if the procedure depends directly on only one table as in numbers 2 and 3 above, the transfer fails. If it depends on > 1 table, it succeeds.

Additional query words: sql6 winnt sproc
Keywords : kbbug4.21a kbbug6.00 kbprg kbtool SSrvStProc SSrvTrans
Version : 4.21a 6.0
Platform : WINDOWS
Issue type : kberrmsg

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.