Microsoft Visual Database Tools Readme |

(c) Copyright Microsoft Corporation, 1997. All rights reserved.

This document provides late-breaking or other information that supplements the Microsoft® Visual Database Tools documentation.

Contents

Database Designer

Query Designer

Installation Issues

Using SQL Trace in Microsoft® SQL Server™

### Database Designer

Printing a Database Diagram

You can print a database diagram on any printer that supports raster graphics. Diagrams print at the current zoom level. If you want to enlarge or reduce your diagram, select a different zoom setting.

To print a database diagram

1. From the File menu, choose Print.

2. In the Print dialog box, select a printer from the Name list. You can also set any of the other available print options. For information about each option, click the What’s This button in the top-right corner of the dialog box, and then click the field that you want to see information about.

3. Choose OK.

The tables and relationships that appear in your diagram will print exactly as shown on the screen with one exception: all of the tables in your diagram appear in their selected state in your printout for better contrast.

### Query Designer

You can update data in the Results Pane of the Query Designer if:

- The primary key column(s) have been included in your query for output.
- The ODBC driver for the data source you're querying against supports SQLPrimaryKeys(). Such drivers include Microsoft SQL Server™, Microsoft Access, Microsoft Visual FoxPro™ v. 3.0 and later, and Oracle.

### Installation Issues

You must install the Microsoft® SQL Server™ 6.5 Service Pack 1 or later to run the Database Designer. For best performance, we recommend Service Pack 2.

### Using SQL Trace in Microsoft SQL Server

Several errors are known to occur when SQL Trace is active.

- You can get a TDS Stream Protocol error when you attempt to save a database diagram.
- You can get a Communications Link Failure during any operation that requires interaction with the server.

If such a problem occurs, close the connection of the person who is running SQL Trace against the server. Then select the data connection in Data View and refresh the connection.