Re: XA and 2000 backwards compatibility

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

As far as I can tell, the 2005 JDBC drivers do support XA on SQL Server
2000, but you have to install a new set of extended stored procedures -
it won't work with the SPs provided with the old JDBC driver.

We are currently using the 2005 JDBC drivers to do XA on an instance of
SQL Server 2000. It seems *fairly* stable. However, it was a clean
instance without the older versions of the extended SPs for XA support.
I don't know if there would be any issues associated with installing
the new SPs over the old ones.

-Matt McGill

Sam Wilson wrote:
Matt,

I am going through the documentation for the SQL Server driver. It states in
one place that the driver is backwards compatible with SQL 2000. However, it
doesn't really say one way or another if this also applies for XA support.

We are currently in the midst of a migration from 2K to 2K5 and need to push
through an application that supports XA. I was hoping to be able to use the
same JDBC driver for servers running 2K and 2K5.

Does that make sense, or should we use the 2K driver on the 2K machines and
the 2K5 driver on the 2K5 machines?

Thanks

Sam Wilson
Ecount, Inc.

"Matt Neerincx [MSFT]" wrote:

In order to process XA transactions, we leverage the MSDTC service on the
SQL Server side (as well as a dll that is loaded inside SQL Server
sqljdbc_xa.dll).

So yes, you will need to go to the SQL Server machine and setup
sqljdbc_xa.dll, and enable XA transactions in MSDTC on the SQL Server
machine. I was planning on writing up a short "step-by-step" document on
this and posting to my blog, but here is the abbreviated version of how to
get XA transactions working with our SQL JDBC 2005 driver:

1. Goto SQL machine, copy sqljdbc_xa.dll to C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn folder (the same folder where sqlservr.exe resides
for your SQL Server instance).
2. Register the dll using the xa_install.sql script (you will need to be
admin on SQL Server to do this).
3. On the SQL Server machine, goto Control Panel | Administrative Tools |
Component Services tool.
Drill down and locate "My Computer" node and right click to get
properties.
4. Goto MSDTC tab on properties, click "Security Configuration" button,
check "Enab;le XA Transactions", click OK.'

Step 4 should restart MSDTC automatically. Note you do not need to enable
anything else here for MSDTC, this is the bare minimum.

5. Stop and restart SQL Server instance so it will pick up new MSDTC
settings.

This should get it working.

--
Matt Neerincx [MSFT]

This posting is provided "AS IS", with no warranties, and confers no rights.

Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"jef" <jef@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1C5FC4AF-1E08-48D2-99CA-27B914E47DA9@xxxxxxxxxxxxxxxx
I am using the new 2005 beta 2 drivers, and I am trying to enlist sql
server
in a distributed transaction with a JMS resource (activemq). I was
assuming
that I needed XA support, but I was a little confused in reading the
xa_install.txt about the MS DTC requirement. If I am using geronimo's
transaction manager, do I need MS DTC? Can I do 2PC-style transactions
between sql server and jms without xa? I was assuming I needed it. If so,
does that basically make the DTC the resource manager for sql server?

Thanks in advance,
--
jef - integralpath.blogs.com




.

Relevant Pages

  • Re: Acessing MS sql from Solaris
    ... Microsoft SQL Server 2000 Driver for JDBC ... delete both the log.txt file and the installation directory. ...
    (comp.unix.shell)
  • Re: SQL Server 2000 database connection problems: Can ANY one help?
    ... other JDBC drivers for SQL Server, ... ADO & SQL Server background, so I know the basics (connection, command, ... >> Looking at the following code snippet, ...
    (comp.lang.java.databases)
  • Re: Acessing MS sql from Solaris
    ... Microsoft SQL Server 2000 Driver for JDBC ... delete both the log.txt file and the installation directory. ...
    (comp.unix.shell)
  • RE: [dbi] Re: MsSQL DBD::ODBC IsNull and undef
    ... I'd guess this is because the SQL Server ODBC driver is looking at your ... Martin J. Evans ... can you run your test script again but creating an OOB log file ...
    (perl.dbi.users)
  • Re: MsSQL DBD::ODBC IsNull and undef
    ... Martin J. Evans ... On 26-Jul-2005 Brian Becker wrote: ... > ensure you tell your driver the type of the column in bind_col. ... > I'd guess this is because the SQL Server ODBC driver is looking at your ...
    (perl.dbi.users)