In my experience I haven't come across something specifically like
this. Have you run the specific query in Management Studio and taken a
look at it?
Quite often coming from a LAMP school myself, I always want to blame my
query issues on php's support of mssql but more often than not its me
looking in the wrong spot. Not to say that this is the case. Sometimes
queries running in 2000 create different execution plans than they do in
2005.
Weaver Hickerson wrote:
Greetings to the group. I have a PHP4 report that has a couple of queries that "go out to lunch" when connected to 2005. Connect back to 2000 and it works fine.
These are based on the mssql_connect, mssql_query, etc.
Any help in getting past this stumbling block would be greatly appreciated. WE are looking to port to PHP5, but of course not overnight and this one came at us out of left field and we already are moved to the 2005 server. Every other php and query seems to work fine.
Is there/are there some tricks/settings for dealing with php4 and SQL Server 2005? (the web server is a separate box from the DB server, by the way..)
Thanks,
--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
