Home >Teratrax Database Manager> Help > Connecting to SQL Server and MSDE

Connecting to SQL Server and MSDE

Before you can work with Teratrax Database Manager, you need to establish a connection to your SQL Server. Whether you are connecting over the Internet, intranet, or simply locally, you need to enter the required information in the Connect dialog.

The Connect Dialog

The Connect dialog is used to connect to an instance of Microsoft SQL Server or MSDE. Enter the following information in the Connect dialog:

• Server Name: name or IP address of the server you are connecting to. For example, SQLServ or SQLServ\Instance2 for a named instance. Use "(local)" for the local server. For the default SQL Server 2005 Express Edition, use (local)\SQLEXPRESS.
• Windows Authentication: indicates that the connection will be authenticated using your Windows account.
• SQL Server Authentication: indicates that the connection will be authenticated using a SQL Server account.
• Login Name: the login name if you are using SQL Server Authentication.
• Password: the password if you are using SQL Server Authentication.
• Remember connection parameters to this server: this option allows you to save the information entered in this window so next time it will connect automatically. Information will be saved with basic encryption.
• Client Network Utility: See Client Network Utility.

Client Network Utility

The Client Network Utility button allows you to configure the client protocols and aliases that Windows should use when connecting to the server. The Client Network Utility is part of the Microsoft Data Access Components (MDAC), which contains ADO.

If you need to connect to a server over the internet, or if your local network supports TCP/IP only, you need to use the TCP/IP protocol. Make sure that TCP/IP is enabled in the Client Network Utility and given top priority (moved to the top of the list or used as the only protocol). If the connection is failing, you can tell which protocol you are using from the error message you get. If the error message starts with [DBNETLIB], you are connecting under TCP/IP. If it starts with [DBNMPNTW], you are using Named Pipes.

In ADO 2.8, no protocols are enabled by default. This does not mean that you cannot connect. It simply means that a default sequence will be engaged in connecting to determine the protocol that will first succeed. Not all versions of ADO default to the same protocols. ADO 2.5 for example, defaults to Named Pipes.

Changing TCP/IP Port

The Client Network Utility lets you change the way ADO connects to SQL Server and MSDE by changing the protocols used. It also provides support for changing the default port (1433) SQL Server is listening on. To change the default port, highlight the TCP/IP protocol then click on the Properties button. Change the port number to new port number and click Ok. If you connect to more than one server and they have different ports, you can create an alias for the server that listens on ports other than 1433 from the aliases tab.

Troubleshooting Connections

To reduce the risks of security vulnerabilities, Microsoft constantly adds security features (like those added in Windows XP SP2) to prevent attacks and secure SQL Server environment. These features make connecting to SQL Server increasingly difficult to troubleshoot. One of the most common error messages users get is "SQL Server does not exist or access denied" or "Specified SQL Server not found". To troubleshoot connection problems, follow the following steps:

1. Verify that SQL Server or MSDE is installed and running: Right-click the "My Computer" icon and select "Manage". Once the management consol is open, navigate to Services and Applications ->  Services. If MSSQLSERVER is in the list of services, then the default instance of SQL Server or MSDE is installed on the computer. Other instances may exist, in which case they will be listed as MSSQL$****, where the asterisks indicate the name of the instance.
2. If you are connecting remotely (to a server on a different machine), make sure your connection is not blocked by any firewalls on either machines including Windows built-in Internet Connection Firewall (ICF) and/or Windows Firewall. Contact your system administrator for firewall configuration.
3. If you are referencing an instance of SQL Server 2000 or MSDE 2000 other than the default instance, use the convention <server_name>\<instance_name> (example ProdServ\Sales).
4. Make sure you don't have an older ADO version (see ADO Versions below for details).
5. Make sure your client protocols are configured properly (see Client Network Utility for details).
6. If you are connecting to a remote server and the server name is not resolved with DNS, use the IP address itself instead of the server name.

ADO Versions

MDAC ships with the Windows operating system. Applications that use ADO can make use of the default version of ADO on the target Windows system. The following is a list of the default ADO versions that ship with Windows:

Visit http://msdn.microsoft.com/data/ for more information about ADO and MDAC downloads.