Re: [PHP-DB] MSSQL stability problem

2004-01-25 Thread Thierry Bothorel
I confirm, I run IIS with php 4.3.2 in Fastcgi with IIS since several months without any problem. -- Thierry Bothorel (Tobias Schlitt) "Frank M. Kromann" <[EMAIL PROTECTED]> a écrit dans le message de news: [EMAIL PROTECTED] > I'm guessing that you are using PHP as ISAPI or Apache module and that

Re: [PHP-DB] MSSQL stability problem

2004-01-24 Thread Frank M. Kromann
I'm guessing that you are using PHP as ISAPI or Apache module and that might not always work with the MSSQL extension. The library (ntwdblib.dll from Microsoft) used for this extension is not thread safe. If you switch to CGI or FastCGI you will not have these problems. - Frank > Stuart wrote: >

Re: [PHP-DB] MSSQL stability problem

2004-01-22 Thread Stuart
Stuart wrote: Robert Twitty wrote: Maybe you are running out of connections. The max connections settings in both php.ini and SQL Server are set to unlimited. Is there another limit I am not aware of? I am now closing the connection to MSSQL at the end of every page and it still does it. I've re

Re: [PHP-DB] MSSQL stability problem

2004-01-22 Thread Stuart
Robert Twitty wrote: Maybe you are running out of connections. The max connections settings in both php.ini and SQL Server are set to unlimited. Is there another limit I am not aware of? -- Stuart On Wed, 21 Jan 2004, Stuart wrote: I have a site that makes heavy use of a local SQL Server databa

Re: [PHP-DB] MSSQL stability problem

2004-01-21 Thread Robert Twitty
Maybe you are running out of connections. -- bob On Wed, 21 Jan 2004, Stuart wrote: > I have a site that makes heavy use of a local SQL Server database. Every > 6-12 hours the site continuously reports not being able to connect to > the database. That is the only info in the warning that's given

[PHP-DB] MSSQL stability problem

2004-01-21 Thread Stuart
I have a site that makes heavy use of a local SQL Server database. Every 6-12 hours the site continuously reports not being able to connect to the database. That is the only info in the warning that's given. The only solution I've found is to restart the Apache and MSSQL services. The [MSSQL] s