The information in this article applies to:
SYMPTOMSIf you cancelled saving a Database Diagram that involved multiple table edits after a previous attempt to save, you might discover that relationships to tables no longer exist the next time you open your diagram. CAUSEThe Database Designer groups all the DDL changes required for tables into separate transactions. In many cases, the Database Designer deletes foreign key relationships that point to a table before it can re-create it in a separate transaction. Should the commit action fail on one of the related tables, the database state will be inconsistent with what is shown in the diagram. If you then close the diagram without saving, you'll lose your relationships. RESOLUTIONIf you encounter an error during a diagram save action, you should use the Query Designer to fix your data or go back into your diagram and remove any constraints that might prevent you from saving the diagram. Once you've corrected the problem, save your diagram changes and the relationships will be restored correctly. STATUSThis behavior is by design. MORE INFORMATIONFor more information regarding how to resolve commit failures when saving diagrams, see the Help topic "Troubleshooting Errors" under Visual Database Tools/Database Designer/Troubleshooting. Steps to Reproduce BehaviorThe following example uses the pubs database that ships with SQL Server.
REFERENCES
Visual InterDev Help: search on "Troubleshooting Errors" under Visual
Database Tools/Database Designer/Troubleshooting.
http://support.microsoft.com/support/vinterdev/ Additional query words:
Keywords : kbDatabase kbVisDBTools kbVisID kbGrpASP kbDtDbDesigner kbDtQDesigner |
Last Reviewed: November 16, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |