ID:               21772
 Updated by:       [EMAIL PROTECTED]
 Reported By:      pvy at novosoft dot ru
-Status:           Bogus
+Status:           Feedback
 Bug Type:         MSSQL related
 Operating System: windows 2000/sp3
 PHP Version:      4.2.3
 New Comment:

Are you guys running under IIS ?


Previous Comments:
------------------------------------------------------------------------

[2004-05-05 08:47:43] reubs at idsdatanet dot com

We have the same problem - but there is an interesting twist. Was
running through the test in a progressive manner.

1. Vanilla install on local machine MSSQL2k/PHP433 - works as expected
without any service packs --- Machine A

2. Vanilla install on remote machine MSSQL2k - unacceptably slow -
response and processing time went from 1 second to 15-20seconds. --
+Machine B - colleague ran a packet sniffer and found fragmented
requests

3. Installed latest service packs on Machine B, fragmented packets are
reduced. Speed is still slow - improvements were minor.

-- here is where you have to read carefully.

4. Installed latest service pack on Machine A (remember machine A had a
version of MSSQL2k but not used as the target DB) - Speed went up to
equivelant of MySQL/PHP, impressive, problem solved(?) - assumption
must install connector service pack upgrade on Web server as well

5. Client complained - no improvement,

6. Uninstalled the MSSQL server on my webserver - installed just the
connectors, ran the MDAC update patches - Result, same as note 2 -
15-20second response time.

Obviously there seems to be a difference in MSSQL Connector DLLs. Have
to look into this (unless someone here know what is going on) but I
must admit my suggestion to them would be a LAMP config.

--sob story - basic rant start
The excessive finger pointing on bug ownership in the end puts us at
risks of losing a key client as we come up to no solution but a lot of
doubts by the client on the platform of choice - and the IS department
having spent a lot of money on MSSQL will blame it on PHP first before
putting the blame on their choice of corporate db.

------------------------------------------------------------------------

[2003-01-21 12:27:09] [EMAIL PROTECTED]

Sorry, but your problem does not imply a bug in PHP itself.  For a
list of more appropriate places to ask for help using PHP, please
visit http://www.php.net/support.php as this bug system is not the
appropriate forum for asking support questions. 

Thank you for your interest in PHP.

There are some networking issues when Linux & Win32 machines
communicate. For example a stock 100mbit lan only operates at 1/3 - 1/2
speed while if both machines run the same OS all 100mbit are
avaliable.
Since this appears to be a networking issue, I am marking this a bogus
(not a php bug).

------------------------------------------------------------------------

[2003-01-21 11:24:59] [EMAIL PROTECTED]

Hi,

I'm unable to reproduce these diferences on my systems.

I have tested the speed on a SQL Server 7.0 and I get almost the same
response times on local and remote connections. In my case the local
connects are slower due to the fact that both PHP and MSSQL server is
competing on the CPU.

If there is a diference from Linux to Windows this must be caused by
old versions of DBLIB used on Windows. I'm working on using FreeTDS on
Windows.

Other factors can be how you configure your MSSQL Server and Clients.
If you don't do anything MSSQL defaults to named pipes (approx 8 times
slover on a network but faster on a local connection compared to
TCP/IP).
You should use the Client Network Configuration tool to specify default
libraries and configure aliases for your local and remote servers. Then
use this alias when connecting to the server.

When you compare PHP and MS Queary Tool you compare apples and oranges.
PHP is build on an old database protocol and MS Query Tool uses the
most modern technology available.

- Frank

------------------------------------------------------------------------

[2003-01-21 03:51:35] pvy at novosoft dot ru

Thank you Joey!
Good work!

------------------------------------------------------------------------

[2003-01-21 03:49:56] [EMAIL PROTECTED]

We've been using PHP hosted on a win32 machine to connect 
to SQL Server 2000.  When the PHP host and the MSSQL host
are the same machine, everything is fine. But when we try
to use seperate hosts for PHP and MSSQL, query times become
unbearably slow.

The odd thing is that I can run the same scripts on the
same network connecting to the same MSSQL server from a Linux box, and
see acceptable response times.

As an example, I did a script that does 1000 iterations
of 'sp_sproc_columns @procudure_name = "some_proc"' in three
different setups.


Setup 1:
  MSSQL and PHP on the Win2k host, call it machine 'A'
  Average Response time over 5 iterations of script: 18s

Setup 2:
  MSSQL on host 'A', PHP on Linux host ('B')
  Average Response time over 5 iterations of script: 41s
  (Given the size of the result set, this is an acceptable
   response time.)

Setup 3:
  MSSQL on host 'A', PHP on seperate Win2k host ('C')
  Average Response time over 5 iterations: 3 minutes, 20s

Clearly, there is something wrong here. I had a different admin set up
a similar network without looking at my php.ini, etc., and he had
similar results.

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/21772

-- 
Edit this bug report at http://bugs.php.net/?id=21772&edit=1

Reply via email to