Configuring Microsoft SQL Server Databases

This chapter describes how to use Microsoft SQL Server databases with the Novell exteNd Application Server. It includes information about using Microsoft SQL Server as a SilverMaster or deployment database. It contains these sections:

For more information For the latest information on supported database versions, see the Novell exteNd Application Server Release Notes.

Basic setup for Microsoft SQL Server databases

You'll perform the following setup steps whether your Novell exteNd Application Server will access a Microsoft SQL Server database via JDBC or ODBC:

Create the database and configure SQL Server.
Create a database login to be used by the application server.

Create the database and configure SQL Server

Before you can install the application server, you must first create the actual SQL Server database (and underlying database devices). You can create these objects using either ISQL or a graphical tool such as SQL Enterprise Manager.

Create the database login

Create a login (with a name such as SilverUserLogin) to be used by the application server. Note the following:

The login cannot have a null password.
You must set the default database for this login to the SilverMaster database you just created. If you do not, you receive error messages during the application server's startup stating The database schema for SilverMaster is out of sync.
For SQL Server 7, create a login using a SQL Server authentication mode and enable the db_owner role for the desired database on the Database Access tab.
The login must have the following permissions: Create Table, Create View, Create SP, Create Default, Create Rule, Backup DB, and Backup Log.

Setting up JDBC access

The application server can connect to Microsoft SQL Server using the JDBC driver supplied by Microsoft.

Install the JDBC driver

You must have the Microsoft SQL Server JDBC driver installed on the machine where the application server will be. It must be able to connect to the destination SQL Server database.

Add the driver path to AGCLASSPATH

The location of the Microsoft SQL Server JDBC driver (JAR files msbase.jar, mssqlserver.jar, and msutil.jar) must be specified in the AGCLASSPATH variable. For Windows, AGCLASSPATH is a system environment variable. For UNIX, you'll find it in the .agprofile file. For NetWare, you need to use the setenv command to set AGCLASSPATH (setenv AGCLASSPATH=path1;path2;path3;...).

For more information For details, see the chapter on data source configuration in the Administrator's Guide.

Setting up ODBC access

The application server can connect to Microsoft SQL Server using the ODBC driver supplied by Microsoft as part of the SQL Server client. There are different versions of this ODBC driver.

Install the Microsoft SQL Server client

You must have the Microsoft SQL Server client software installed on the machine where the application server will be. Your client must be configured to connect to the destination SQL Server database.

Create the ODBC System DSN entry

Configure an ODBC System DSN entry for the SilverMaster or deployment database.

Procedure To create the ODBC System DSN for a Version 7 or 2000 database:

Add an entry using SQL Server as the driver type.
Enter the server name for the target SQL Server.
Enter the SQL Server user authentication information for the login you created and click Next.
Select the proper default database name.
Deselect Use ANSI quoted identifiers.
Deselect Use ANSI nulls, paddings, and warnings and click Next.
Accept the proper language and region settings, then click Finish.

Using the database with the application server

Now you're ready to access the Microsoft SQL Server database from the application server. This enables you to do any of the following, as appropriate:

Install the application server and point to that database as the SilverMaster (as described in Installing Novell exteNd)
Add that database to the application server for use as a deployment database
Add a connection pool to the application server for accessing that database

For more information, see the chapter on data source configuration in the Administrator's Guide.