Connection problem to SQL Server 2000

Question

I have a local installation of MSSQL 2000, that doesn't seem to use any port as a listener. when checking the log I can see that even though I said it should use a TCP/IP connection, it says it uses a shared memory (I guess the reason is that the installation I did is not for a server but only for running on my machine).
How can I define through BPEL the connection to this kind of MSSQL? can I define a connection that will run on the named pipes of the SQL server?
Thanks in advance.

Answer 1

Hi Ophir,
I tried this exercise of connecting to SQL Server myself via jdbc and I wrote a new section for the developer's guide based on it. It was not completely painless. For your specific question the SQL Server Express install sets up connectivity by either 'shared memory' or 'named pipes' by default, but you can easily add a TCP/IP listener (for me via the SQL Server Configuration Manager), which is mandatory for jdbc access. Please see the section 'TCP Port' below.
Not sure if you have it, I am cutting and pasting from the 10.1.2.0.2 DBAdapter guide:
(Oracle® Application Server Adapters for Files, FTP, Databases, and Enterprise Messaging User's Guide
10g Release 2 (10.1.2))
Using a Microsoft SQL Server Database
When using a Microsoft SQL Server database, follow the database connection steps in Chapter4, "Design Time" and use the following information:
MS JDBC Driver
URL: jdbc:microsoft:sqlserver://localhost\NAME:1433;SelectMethod=cursor;databasename=???
Driver Class: com.microsoft.jdbc.sqlserver.SQLServerDriver
Driver Jar: .\SQLServer2000\msbase.jar, msutil.jar, mssqlserver.jar
DataDirect Driver
URL: jdbc:oracle:sqlserver://localhost
Driver Class: com.oracle.ias.jdbc.sqlserver.SQLServerDriver
Driver Jar: .\DataDirect\YMbase.jar, YMoc4j.jar, YMutil.jar, YMsqlserver.jar
Note the following when connecting to a SQL Server database:
User name and password
o
SQL Server 2005 installs with Windows authentication as the default. Therefore, you do not log in with a user name and password; rather, your Windows user account either has privilege or does not. JDBC requires you to provide a user name and password.
According to support.microsoft.com, "Microsoft SQL Server 2000 driver for JDBC does not support connecting by using Windows NT authentication." See
http://support.microsoft.com/default.aspx?scid=kb;en-us;313100
However, the DataDirect driver specification states that it does.
If you use your Windows user name and password, you may see something like the following:
[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Login failed for user
'DOMAIN\USER'. The user is not associated with a trusted SQL Server
connection.[Microsoft][SQLServer 2000 Driver for JDBC]
An error occured while attempting to log onto the database.
You must select mixed mode authentication on a clean installation.
o
On a Microsoft SQL Server 2000 Express Edition installation, the system username is su and the password is whatever you provide.
Connect string
From the sqlcmd login, you can infer your connect string, as in the following examples:
Example 1:
sqlcmd
1>
jdbc:microsoft:sqlserver://localhost:1433
Example 2:
sqlcmd -S user.mycompany.com\SQLExpress
1>
jdbc:microsoft:sqlserver://user.mycompany.com\SQLExpress:1433
Example 3:
sqlcmd -S user.mycompany.com\SQLExpress -d master
1>
jdbc:microsoft:sqlserver://user.mycompany.com\SQLExpress:1433;databasename=
master
A full URL is as follows:
jdbc:microsoft:sqlserver://serverName[\instanceName]:tcpPort[;SelectMethod=cursor][;databasename=databaseName]
Database name
If you must explicitly supply the database name, but do not know it, go to
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
If you see a file named master.mdf, then one of the database names is master.
TCP port
Make sure that SQL Server Browser is running and that your SQL Server service has TCP/IP enabled and is listening on static port 1433. Disable dynamic ports. In SQL Native Client Configuration/Client Protocols, make sure that TCP/IP is enabled and that the default port is 1433.
JDBC drivers
You must download the JDBC drivers separately. From www.microsoft.com, click Downloads and search on jdbc. You can also try using the DataDirect driver.
Thanks
Steve