DD 6 and MS Sql Server

Dwayne

Help - I'm pullingmy hair out over this (and I don't have any to spare)

Env: TS 6.1/OD (DD) 6.0, W2K3

I'm trying to deploy metadata from TS 6.1 to DD 6 in a standalone deployment, using a user-defined schema. Sounds simple enough, right?

I was able to connect to the database easily enough, using the 'vendor="microsoft-microsft"' database setting, but then I got this error:

ERROReployment to a Microsoft SQLServer database using user-defined dbschema is not supported with JDBC-ODBC bridge. You should use Inet-UNA JDBC driver.Refer to DataDeploy Administration manual.

I think to myself, "Self, why don't you try the microsoft-inetuna driver instead?" So I did, but got an error indicating that the class wasn't found. So I zipped over to the Microsoft site to download it. Got it installed, and I'm no longer getting the "class not found" error. Instead, I'm back to the first error!

Now, this is allowing the server to choose the "default" database for this user, because that's the one I want. But I thought I'd see what happens if I explicitly set the database. Well, if I do that, it won't connect at all.

Here's the database.xml snippet that I'm using:

<database name="CMS"
              db="jdbc:inetdae:HOUEBIZ250:1433?database=CMS"
              user="cms"
              password="****"
              vendor = "microsoft-inetuna"
              max-id-length = "128" />

If I just use 'db="HOUEBIZ250"' I connect OK, but I get the above error. With the text as shown, I get

Setting up TDbSchemaSynchronizer.
url      : jdbc:inetdae:HOUEBIZ250:1433?database=CMS&sql7=true
login    : cms
login timeout=3
Connecting to the database...
Try connecting using jdbc:inetdae:HOUEBIZ250:1433?database=CMS&sql7=true... 
SQL failure
ERROR:ERROR: Could not connect to [jdbc:inetdae:HOUEBIZ250:1433?database=CMS&sql7=true]

*******************************************************
SQLException occured in JdbcCheckup:MakeConnection()
Exception Message: []Login failed for user 'cms'.
Vendor Error Code: 18456
SQL state: 28000

Of course, the username and password are the same ones that worked just a minute ago for the version without a specific database.

--

Current project: TS 5.5.2/6.1 W2K

Edited by Dwayne on 09/24/04 12:13 PM (server time).

Dwayne

OK. Found the problem.

ARGH!!!

The password for the account that's used to access the DB contained a '$'. DD was very considerately treating that as a parameter variable, and substituting in nothing. So the connection failed, but it "fell back" to NTLM. Since my NT account WAS granted access, it succeeded with an ODBC connection.

Once I put two '$' characters where I wanted one, it worked fine.

I want to cry. :-(

--

Current project: TS 5.5.2/6.1 W2K