About Code Examples in the Documentation

Microsoft Drivers for PHP for SQL Server

Collapse image Expand Image Copy image CopyHover image

There are several points to note when you execute the code examples in the Microsoft Drivers for PHP for SQL Server documentation: 

  • Nearly all the examples assume that SQL Server 2005 or later and the AdventureWorks database are installed on the local computer.

    For information about how to download a free editions and trial versions of SQL Server, see SQL Server 2008 Overview.

    Although most editions of SQL Server come with the AdventureWorks database, it can be installed separately. For information about how to download the AdventureWorks database, see Microsoft SQL Server Samples and Community Projects. For information about how to install the AdventureWorks database, see Walkthrough: Installing the AdventureWorks Database.

  • Nearly all the code examples in this documentation are intended to be run from the command line, which enables automated testing of all the code examples. For information about how to run PHP from the command line, see Using PHP from the command line.

  • Although examples are written to be run from the command line, each example can be run by invoking it from a browser without making any changes to the script. To achieve nice output formatting, replace each "\n" with "</br>" in each example before invoking it from a browser.

  • For the purpose of keeping each example narrowly focused, correct error handling is not done in all examples. It is recommended that any call to a sqlsrv function or PDO method be checked for errors and handled according to the needs of the application.

    An easy way to obtain error information when an error is encountered is to exit the script with the following line of code:

      Copy imageCopy Code
    die( print_r( sqlsrv_errors(), true));

    Or, if you are using PDO,

      Copy imageCopy Code
    print_r ($stmt->errorInfo());
    die();

    For more information about handling errors and warnings, see Handling Errors and Warnings.

See Also