Viewing 7 posts - 1 through 7 (of 7 total)
Apparently, using DBI and ADO is the only working way to do this right now.
I was able to get it working.
October 2, 2007 at 3:23 pm
SQL Server 2000 uses UCS-2. We specifically upgraded to SQL 2005 because it does support UTF-8.
The querys did not work with SQL Server 2000 because of the UCS-2, but...
April 24, 2007 at 9:50 am
I don't know that it is a perl problem. From perl I can print UTF-8 characters through the web server just fine.
The characters are correct in the table, I...
April 23, 2007 at 2:18 pm
The data is stored as unicode (nvarchar).
It's listed correctly in the db. It's just that after it goes through the odbc driver to perl, it is losing the encoding.
Is...
April 2, 2007 at 10:03 am
That's exactly what I was looking for.
Thanks.
December 12, 2006 at 4:02 pm
Problem Solved.
After running a packet sniffer for a while I discovered that there was an ARP request for the IP of the database server right before the problem. So...
June 11, 2003 at 1:57 pm
We are only using TCP/IP with and ODBC connection. SP3a on the sql server and Windows 2003 server.
Last night I set up a countinuous ping from the database server...
June 10, 2003 at 6:57 am
Viewing 7 posts - 1 through 7 (of 7 total)