To import an existing Microsoft OLE DB provider for SQL Server 7.0 data source object

1.    Click the Import button in the CONNX Data Dictionary Manager window.

2.    The Import CDD dialog box appears. Select SQL Server from the Import Type list box in the Import CDD dialog box.



Important:
This direct OLE DB connection to SQL Server only works with SQL Server 7.0 or later. If you are using a SQL 6.x database, you will need to use an ODBC connection. To Import Objects From an SQL Server 6.x or 7.0 ODBC provider data source.

Note:
Some SQL Servers are configured for NT Integrated Security, which uses your system account information, while others require a user name and password. Consult the configuration of your SQL Server before selecting a mode. Select a Windows NT authenticated login or an individual user name and password that matches your configuration.

3.    Select OLE DB Provider under Select Provider Type, and then click the Select Provider button in the Logon Information pane.

4.    Select Microsoft OLE DB Provider for SQL Server in the Data Link Properties dialog box. Click the Next button or the Connection tab.

image\sql_1.jpg

5.    Enter a server name in Item 1 on the Connection tab in the Data Link Properties dialog box.

image\sql_2.jpg

6.    Enter a user name and password or select NT authentication in section 2.

Important: If you open the list box in Item 1, it uses the SQLOLEDB Enumerator, which attempts to make network calls that are implemented only on NT 4.0 or Windows 2000 systems. The list box also includes both SQL 6.5 and SQL 7.0 servers, but this OLE DB provider only works for SQL 7.0.

Note:
For Windows 95 or 98 systems, the list box in Item 1 is always blank and you must enter the server name manually.

Note:
SQL Server 7.0 documentation uses the word "database" for the word "catalog."

7.    Select a catalog from the list box in Item 3. SQL Server loads the selected catalog automatically. Click the Test Connection button to verify that the SQL catalog is available. Click the OK button. If Item 3 is left blank, the user’s default catalog is used.
If you have unattached SQL database files (consult SQL Server documentation), you may reattach the database file as a catalog by selecting Attach a database file as a database name. The system mounts that database file and uses it as the current catalog.

8.    The Import CDD dialog box appears. Reenter the SQL password, if required.

9.    Normally, only user-defined tables can be selected for import. Select the Include System Tables check box to enable the import of non-user-defined tables.

10.  Select the Get Statistics check box to identify the table sizes. This is used by CONNX query optimization. Click the OK button.

11.  The CONNX Import Table Selection dialog box appears. Click the Add or Add All button to move the catalogs to the Select Tables for Import pane.

image\sql_4.jpg

12.  Click the OK button to import the selected catalogs into CONNX. The imported catalogs appear in the list of accessible objects in the CONNX Data Dictionary Manager window.

image\sql_5.jpg

Troubleshooting

If, when connecting to SQL Server 7.0, a blank table appears in the CONNX Import Table Selection dialog box in step 11, it means that the user may not have sufficient privileges to access the catalog. The SQL Server administrator should use the Enterprise Manager tool to change the security level for that user to enable access to the table. In the SQL Server Enterprise Manager, the Properties dialog box of each user has a database access tab that can be used to control access levels.