Dear PHP developers and SQL Server users,

We, the PHP group in the SQL Connectivity product team, received a lot of feedback in our previous survey in Oct 2009, and we responded to the feedback by delivering a PDO driver in our v2.0 release. After releasing our CTP2 for v2.0 of the driver, we have been very busy responding to feedback and preparing the code for the final release. While this work is in progress, it is time for to review our priorities once again with our primary audience.

While we always listen and respond to feedback on our forum / blog and invite your participation at any time, surveys are great for capturing structured feedback. You and your organization are key stakeholders in this process and need your input in this survey, which should take less than 10 minutes to complete.

Now that we have the 2 major categories of drivers, the SQLSRV driver with the procedural API and the PDO_SQLSRV driver implementing PDO, with basic support for SQL Server it is now time to consider features that expose the rich functionality offered by SQL Server and thus enrich your PHP applications even more. The feedback provided is extremely valuable and help us make the necessary adjustments in our roadmap.

This survey will be open until August 16th, 2010 5:00PM PST (Seattle time zone).

The SQL Server PHP team truly appreciates your effort in completing this survey.

Thank you,

Ashay Chaudhary
Program Manager - PHP, SQL Connectivity
Database Systems Group, Microsoft Corp.

Comments are disabled for this post since the survey provides adequate opportunity for feedback. Some of the features have short descriptions below to provide better clarity.

  1. Paged results: we blogged on a couple of ways to do this in the past, there are a few more methods available too; the idea here is that the driver does it in a more comprehensive yet performant way.
  2. Multi-core CPU utilization: while PHP scripts are single threaded, the driver can become multi-threaded to enable some asynchronous operations to improve performance.
  3. Resultset cache in cache server: the resultset is cached in a cache server (for example, memcached, etc.) which is accessible to other web servers for faster retrieval of the data.
  4. Client-side resultset cache: the resultset is cached on the web server itself; this feature can be synchronized to use the cache server if one is available.
    (the rest are linked directly in the survey)