In a multiuser environment, deleting database objects from the database can affect other users. If another user deletes a database object that appears in your database diagram, the effect of the deletion on your diagram depends on where the object was deleted.
| Where the object was deleted | How your database diagram is affected |
|---|---|
| In another copy of your database diagram | The deleted object is removed from your diagram. |
| In a different database diagram | The deleted object is removed from your diagram. |
| In the database | If your diagram has no unsaved changes to that object, the object will be removed from your diagram the next time you open it.
If your diagram contains unsaved changes to that object, the object will remain in your diagram. You can re-create it in the database by saving your diagram. |
Note Re-creating a deleted object creates a new definition of that object in the database; it does not restore the data that was deleted when the object was deleted.
For example, if the titles table is deleted in the database and you have unsaved changes to the titles table in your database diagram, then saving your diagram will create a new titles table in the database. Any data that existed in the titles table before it was deleted is not restored.