Our story is.... We started building our application back in 2002 on FreeBSD/Apache with PostgreSQL. Than company we are working for became bigger and they bought SQL 2000 server and we had to switch to MS SQL 2000. Now company became even more bigger and they decided that keeping FreeBSD server which nobody knows and nobody wants to learn in IT department is a risk and we have been asked to move from FreeBSD/Apache to Win 2000/ IIS 5. Back in 2002 we choose ADODB as db abstraction library. With OS switched we noticed a few things: 1) ado-mssql driver which uses mssql_* calls in PHP has a problem of returning only first 255 characters for VARCHARs. I can not agree that casting varchars as text in SQL queries solves this problem (it may be solves it for simple applications) as TEXT datatype has many limitations on its use in SQL queries - you can't use LIKE and DISTINCT and other. 2) ado-ado_mssql. This one uses not ntwdblib.dll but Win COM object ADO (if I am right) There are no problems with varchars but COM object does not like DATETIMEs less than 1970 and all your employees which were 'lucky' to be born before 1970 suddenly become all born in 1970. I am not sure but it looks like choice of platform - PHP on IIS with MSSQL is not a good idea. And by trying to minimize IT department risk (necessity to support OS they do not know) we maximize our application support issues. If anybody can suggest or share experience - please do. Thank you, Igor Kryltsov -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
