The best extension for accessing MS SQL Server is the odbtp extension at http://odbtp.sourceforge.net. The odbc and mssql extensions both have limitations when used with SQL Server 2000. mssql ext: - Uses the obsolete, unsupported and non thread safe DB-Library. - Does not support varchar(>255), nvarchar and ntext fields. - Cannot use FOR XML clause in SQL. odbc ext: - Uses ODBC 2 instead of ODBC 3. - Does not provide support for stored procedures. - Does not support nvarchar and ntext fields. The odbtp extension is considerably faster than the odbc extension, and is just as fast as the mssql extension. It also provides support for all of the mssql_* functions, which means it can be used as a "seemless" replacement for the mssql extension. And, unlike the odbc and mssql extensions, the behaviour of the odbtp extension is the same on Linux/UNIX platforms. -- bob On Tue, 6 Apr 2004, Svensson, B.A.T. (HKG) wrote: > >>You have made sure that the ms sql extension is available in the > >>php ini file, as well made sure that the ms sql dll is in the > >>same directory as php.exe? > > >If possible don't use the mssql extension but use the ODBC one. To my > >knowledge it has not changed since MSSQL 6.5 and is unreliable. You can > >run into problems if you run a query and then do a header location. > > I am using php as fast-cgi on the same type of server configuration, i.e. > Win2003, IIS6, MSSQL server 2000, etc, and have exprienced no real problem > yet. > > So I am curious about this. Would you like to explain this a little bit more > in details? -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
