Access both SQL Server and Sybase databases

For a system administrator, to manage multiple database servers in a network at the same time or multiple database servers that are divided into different networks in the Internet, the problem of accessing these database servers at the same time is resolved first. In general, a variety of databases must be connected using their own corresponding client tools, and cannot connect to another database. Microsoft's SQLSERVER6.0 database is developed from the SYBASE4.2 database, and its own client tools cannot connect to SYBASE10 or SYBASE11 databases. In addition, the SYBASE11 client-side tool WISQLL32 can perform any of the selected portions of a SQL file in a segmented way, which makes it much easier to manage the database server, debug stored procedures, and triggers. This feature is not available at Microsoft's SQLSERVER6.0 database client with tools Isql_w.

In the work practice, the author discovers that as long as the SYBASE11 client is properly configured, after the WISQLl32 menu is disconnected from a connected database server, the other database server in the network is not restarted, You can access both the Microsoft SQLSERVER6.0 database and the SYBASE11 (or 10) database at the same time. It provides great convenience both for managing multiple database servers (especially SQLSERVER6.0 databases), and for porting stored procedures and triggers between SQLSERVER6.0 and SYBASE11. This article on the author's own implementation methods to provide you with reference.

A System environment

For simplicity, it is assumed that only one network server in a single network environment, with MSSQLSERVER6.0, SYBASE11 (or SYBASE10) installed on this network server, is not recommended for both SYBASE11 and 102 versions. Do not consider a single network of multiple servers or multiple network server environment on the Internet. However, in any environment, the same method can be used to achieve WISQLL32 access to the database servers distributed on one or more network servers.

1. Network server: WINDOWSNT3.51 or 4.0 network operating system, memory 64MB above, Pentium 133 above, network protocol for TCP/IP, primary domain controller name RMYH, network server computer name DBServer.

2. The MSSQLSERVER6.0 database server installed on the DBServer network server is named DBServer (with the same name as the network server), SYBASE11 the database server contains SYBASE11 (SQL Server), Sybase11-bs (Backup server), Sybase11-ms (monitor server), SYBASE11-HS (history server) four database servers (SYBASE10 database server contains only SYABSE10, Sybase10-bs, sybase10-ms three database servers).

3. Client: Chinese WINDOWS95,SYABSEFORWINDOWS95 client Tool

Two Configuring the SYABSEFORWINDOWS95 Client tool

Sqledit is a platform-independent program for configuring client connections, Sqledit is used to edit files named Sql.ini in the Sybase root directory, or to manually edit Sql.ini files, but it is easier to make use of Sqledit graphics tools and to push errors to Sybase. For the use of Sqledit, please refer to Sybase's instructions. This article mainly discusses how to select parameters in Sql.ini to enable Wisql to access both MSSQLSERVER and SYBASE11 database servers.

WindowsNT can choose NetBEUI, ipx/spx, TCP/IP three network protocols to build the network, SYBASE11 (or SYBASE10) when the database server is installed, the Net-library driver is generated according to the network protocol. Three network protocols can generate a net-library driver named Nlmsnmp (named pipe), which for TCP/IP network protocol, but also to generate a nlwnsck (soft socket) of the net-library driver, so I choose to use tcp/ IP windowsnt Network as an analysis of the environment.

The contents of the Sql.ini file configured with Sqledit or editing software are as follows (Sql.ini file in C:\sybase\ini directory):

[MSSQL6.0]

$BASE $00=nlmsnmp,\\ dbserver \pipe\sql\ Query

$BASE $01=nlwnsck,dbserver,1433

query= $BASE $00; $BASE $01;

$BASE $02=nlmsnmp,\\dbserver\pipe\sql\query

$BASE $03=nlwnsck,dbserver,1433

master= $BASE $02; $BASE $03;

[SYBASE11]

$BASE $00=nlwnsck,dbserver,5000

$BASE $01=nlmsnmp,\\dbserver\pipe\sybase\query

master= $BASE $00; $BASE $01;

$BASE $02=nlwnsck,dbserver,5000

$BASE $03=nlmsnmp,\\dbserver\pipe\sybase\query

query= $BASE $02; $BASE $03;

[Sybase11_bs]

$BASE $00=nlwnsck,dbserver,5001

$BASE $01=nlmsnmp,\\dbserver\pipe\sybase\ Backup

query= $BASE $00; $BASE $01;

$BASE $02=nlwnsck,dbserver,5001

$BASE $03=nlmsnmp,\\dbserver\pipe\sybase\backup

master= $BASE $02; $BASE $03;

[Sybase11_ms]

$BASE $00=nlwnsck,dbserver,5002

$BASE $01=nlmsnmp,\\dbserver\pipe\sybase\monitor

master= $BASE $00; $BASE $01;

$BASE $02=nlwnsck,dbserver,5002

$BASE $03=nlmsnmp,\\dbserver\pipe\sybase\monitor

query= $BASE $02; $BASE $03;