I am using MSSqlServer 2000, and i find that it makes a great database. Now that MS has finally released their own driver (you have to dig a little on their site) you can just use that. Take a look at the torque documentation on how to set it up.
Eric -----Original Message----- From: Eric Dobbs [mailto:[EMAIL PROTECTED]] Sent: Sunday, April 28, 2002 11:26 PM To: Turbine Users List Subject: Re: Trailing Spaces in SQL Server Fields On Sunday, April 28, 2002, at 08:33 PM, Chris K. Chew wrote: > Ah, I looked into the odbc configuration and found "Use ANSI nulls, > paddings > and warnings" checked. I unchecked it, logged in, and sure enough...the > trailing spaces weren't there. Thanks for the tip. glad it helped. > What do you use instead of ODBC? JDBC of course. 8^) Sun's JDBC-ODBC bridge is documented as being unsuitable for production deployment (last I looked, anyway). We used SQL Server very briefly when marketing asked if we could support it. At that time JDBC drivers for SQL Server were scarce or prohibitively expensive for our application. We experimented with the JDBC-ODBC bridge (which is when we ran into the padding problem). Anyway, we switched to using (and bundling) SapDB. (http://sapdb.org) It includes a JDBC driver. Haven't touched ODBC since. -Eric -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
