Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Saving a Database Diagram 2
- Thread starter krotha
- Start date
-
1
- #2
I not sure about SQL Server 2000 but if it's the same as 7.0 (I assume it will be) then I know of no method of copying your diagram to a file.
The actual database diagrams are held in the system table, called dtproperties which is unique to each database.
This diagram is very much linked to the database in which it resides i.e. the tables within the database map to the tables within the diagram.
If you wanted to send this to some else then you would have to send a SQL Server database which included all the table structures which were shown on the diagram.
If it is just a hard copy of the layout they need then you could print to a file and send it that way.
Rick.
The actual database diagrams are held in the system table, called dtproperties which is unique to each database.
This diagram is very much linked to the database in which it resides i.e. the tables within the database map to the tables within the diagram.
If you wanted to send this to some else then you would have to send a SQL Server database which included all the table structures which were shown on the diagram.
If it is just a hard copy of the layout they need then you could print to a file and send it that way.
Rick.
-
1
- #3
- Thread starter
- #4
Yes I'm afraid you’re correct. You will have to put the diagram onto Viso from scratch. I know it is like re-inventing the wheel again but it's the only way.
At my site we use Visio to document our entire database schema's (at an overview level) as it's much flexible than the SQL Server diagram editor. I do use the SQL database diagrams to sub divide my database tables into logical modules. These diagrams show the appropriate tables and their column properties. I also use the SQL database diagrams to script any structure changes, which may be required.
A print of the Viso overview diagram and subsequent SQL Server module diagrams is normally sufficient for all my developers to work from.
If you have fairly static databases this method is not too much of a problem to keep control of.
However If your are constantly doing changes then a 3rd party tool such as ERWIN might be worth investing in. It does a lot more than just the diagrams so might be worth having a look at.
Rick.
At my site we use Visio to document our entire database schema's (at an overview level) as it's much flexible than the SQL Server diagram editor. I do use the SQL database diagrams to sub divide my database tables into logical modules. These diagrams show the appropriate tables and their column properties. I also use the SQL database diagrams to script any structure changes, which may be required.
A print of the Viso overview diagram and subsequent SQL Server module diagrams is normally sufficient for all my developers to work from.
If you have fairly static databases this method is not too much of a problem to keep control of.
However If your are constantly doing changes then a 3rd party tool such as ERWIN might be worth investing in. It does a lot more than just the diagrams so might be worth having a look at.
Rick.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question