Re: Msg 20009, Level 9, State 0, Server OpenClient, Line 0

print_r(get_loaded_extensions());

Array ( [0] => xmlwriter [1] => libxml [2] => xml [3] => wddx [4] =>
tokenizer [5] => sysvshm [6] => sysvsem [7] => sysvmsg [8] => standard
[9] => SimpleXML [10] => sockets [11] => soap [12] => SPL [13] => shmop
[14] => session [15] => Reflection [16] => posix [17] => mime_magic
[18] => mbstring [19] => iconv [20] => hash [21] => gettext [22] => ftp
[23] => filepro [24] => exif [25] => dom [26] => dba [27] => date [28]
=> ctype [29] => calendar [30] => bz2 [31] => bcmath [32] => zlib [33]
=> pcre [34] => openssl [35] => xmlreader [36] => apache2handler [37]
=> mysql [38] => mysqli [39] => imap [40] => gd [41] => sybase_ct )






On Jan 24, 9:40 am, "SybaseNeal" <nstac...@xxxxxxxxx> wrote:
Hello,

Sybase's CT-Library API is not compatible with MS SQL Server.
CT-Library uses TDS 5.0.

Sybase's DB-Library API works with some older versions of MS SQL
Server.
DB-Library uses TDS 4.6 by default but can be configured to use TDS
5.0:

http://www.freetds.org/faq.html#Does.FreeTDS.support.Microsoft.servers

It also looks like PHP can be configured for ODBC access. I don't know
if
there are compatibility issues with Microsoft SQL Server using this
access
method:
http://www.freetds.org/userguide/php.htm

In case you aren't aware of the history between Microsoft and Sybase,
at
one point in history, Sybase sold the source code for the database to
Microsoft. DB-Library was highly compatible at first. But as
Microsoft
started development on their own, Microsoft SQL Server became less
and less compatible with Sybase's DB-Library API.
This link explains the history fairly well:
http://en.wikipedia.org/wiki/Microsoft_SQL_server

Thanks,
Neal

.