Where do I get the ODBC Drivers

I am working off of downloaded media from the support site and am trying to install a test environment. Where do I get the ODBC drivers for TS to connect to a SQL server. I.E where do I point the installer to look for them. This is on a Windows 2003 server.

Find more posts tagged with

Comments

Migrateduser

I can't think of any TeamSite functionality that relies on an ODBC connection. There are numerous pieces of functionality that require a jdbc connection to a server, but these generally ship with TeamSite. The exception are drivers for the event subsystem. Can you be a bit more specific about what you are actually trying to accomplish, and the make and model of the database you are attempting to communicate with?

Migrateduser

The event subsystem is what I am trying to get working. Database is MSSQL

smenon

We are not allowed to ship the JDBC drivers for MS SQL Server. Those drivers should be available as part of your MS SQL Server installation. Your DBA might know where to find it. Copy those drivers to a location that is accessible by the TeamSite installer and the installer will pick it up and copy it to the appropriate location in TeamSite.

--Sunil Menon
Sr. Product Manager
Interwoven, Inc.

stefanmaier

Hi,
what's with od.602.ddadmin.pdf, page 92:

"Use JDBC type 4 drivers from i-net software if you are using Microsoft SQL Server 2000.
The i-net driver is packaged with OpenDeploy and resides in the following location:
od-home/drivers/UNA2000.jar."

So we have to use original MS drivers if we're working with the event subsystem
and the shipped una2000.jar if we're working with OD/DD?
Is this right?

@Lawrence: You need mssqlserver.jar, msbase.jar, msutil.jar, see page 34f in ts.650a.admin.pdf (I assumed that you're using TS6.5)

Stefan

Migrateduser

They are also downloadable from Microsoft.

http://www.microsoft.com/downloads/details.aspx?familyid=4f8f2f01-1ed7-4c4d-8f7b-3d47969e66ae&displaylang=en

BTW - The install documentation for this has to be some of the worst ever produced. It doesn't help that the two KB articles about it imply that you should have the JDBC drivers in a lib directory on your sql server, which might sometimes be true, but usually won't.