(No version information available, might only be in Git)

sqlsrv_executeExecuta uma declaração preparada com sqlsrv_prepare()


sqlsrv_execute(resource $stmt): bool

Executa uma declaração preparada com sqlsrv_prepare(). Esta função é ideal para executar uma declaração preparada várias vezes com diferentes valores de parâmetro.



Um recurso de declaração retornado por sqlsrv_prepare().

Valor Retornado

Retorna true em caso de sucesso ou false em caso de falha.


Exemplo #1 Exemplo de sqlsrv_execute()

Este exemplo demonstra como preparar uma declaração com sqlsrv_prepare() e reexecutá-la várias vezes (com diferentes valores de parâmetro) usando sqlsrv_execute().

= "serverName\sqlexpress";
$connectionInfo = array( "Database"=>"dbName", "UID"=>"username", "PWD"=>"password");
$conn = sqlsrv_connect( $serverName, $connectionInfo);
$conn === false) {
print_r( sqlsrv_errors(), true));

$sql = "UPDATE Table_1
SET OrderQty = ?
WHERE SalesOrderID = ?"

// Inicializa parâmetros e prepara a declaração.
// Variáveis $qty e $id estão vinculadas à declaração, $stmt.
$qty = 0; $id = 0;
$stmt = sqlsrv_prepare( $conn, $sql, array( &$qty, &$id));
if( !
$stmt ) {
print_r( sqlsrv_errors(), true));

// Configura as informações SalesOrderDetailID e OrderQty.
// Este array mapeia o ID do pedido para a quantidade do pedido em pares chave=>valor.
$orders = array( 1=>10, 2=>20, 3=>30);

// Executa a declaração para cada pedido.
foreach( $orders as $id => $qty) {
// Porque $id e $qty estão vinculados a $stmt1, seus valores atualizados
// são usados com cada execução da declaração.
if( sqlsrv_execute( $stmt ) === false ) {
print_r( sqlsrv_errors(), true));


Quando você prepara uma declaração que usa variáveis como parâmetros, as variáveis são vinculadas à declaração. Isso significa que se você atualizar os valores das variáveis, na próxima vez que executar a declaração, ela será executada com valores de parâmetro atualizados. Para declarações que você planeja executar apenas uma vez, use sqlsrv_query().

Veja Também

add a note

User Contributed Notes 3 notes

8 years ago
If you're used to working with sqlsrv_query, you're probably used to the following flow:

= "SELECT * FROM mytable WHERE id=?";
$result = sqlsrv_query($conn, $query, array($myID));
$row = sqlsrv_fetch_array($result);

Given that, you might think the following works:

= 0;
$query = "SELECT * FROM mytable WHERE id=?";
$stmt = sqlsrv_prepare($conn, $query, array(&$myID));
$result = sqlsrv_execute($stmt);
$row = sqlsrv_fetch_array($result);

It doesn't. The reason is that sqlsrv_execute, as noted above, returns true or false on success or failure, respectively. The variable that has your result is actually $stmt. Change the last row to

= sqlsrv_fetch_array($stmt);

and it works as expected.
esundberg at nitelusa dot com
4 years ago
Working PDO Prepare and Execute Example

print "<h1>PDO Example</h1>";

print "<h2>PDO Connection</h2>";
try {
$pdo = new PDO("sqlsrv:server=$sql_server;Database=$sql_database",$sql_username,$sql_password,['ReturnDatesAsStrings'=>true]);
} catch(PDOException $e) {
echo "Connection failed: " . $e->getMessage();
die("Database Connection Error");


print "<h2>Check for PDO Connection</h2>";
if($pdo === false) {
print "No DB Connection<br>";
} else {
print "Good DB Connection<br>";

print "<h2>PDO Query Example 1 with SQL Injection</h2>";
print "I Personally prefer pdo due to binding of paramaters by name.<br>";
$sql = "SELECT username, active FROM users WHERE username = :username";
print "SQL: $sql\n";
$stmt = $pdo->prepare($sql);
$stmt->bindParam(':username', $username);
while($r = $stmt->fetch(PDO::FETCH_OBJ)) {

PDO Example
PDO Connection
Check for PDO Connection
Good DB Connection
PDO Query Example 1 with SQL Injection
I Personally prefer pdo due to binding of paramaters by name.
SQL: SELECT username, active FROM users WHERE username = :username
stdClass Object
[username] => admin
[active] => 1
vavra at 602 dot cz
6 years ago
If the sql contains INSERT, UPDATE or DELETE statements, the number of affected rows must be consumed. The sqlsrv_query returns a sql cursor that must be read to finish the transaction, if the result is non false. This same is valid for sqlsrv_execute. In this case the cursor must be also read using the prepared statement handle $smt.

Another solution is to place SET NOCOUNT ON at the top of the sqlsrv statement and all called procedures, functions and triggers.

We've practically observed it with sql statement with 500 inserts but only 368 was inserted without false returned. Prefixing by SET NOCOUNT ON or reading a cursor all rows were inserted.

See Processing Results (ODBC): https://docs.microsoft.com/en-us/sql/relational-databases/native-client-odbc-results/processing-results-odbc Each INSERT, UPDATE, and DELETE statement returns a result set containing only the number of rows affected by the modification. This count is made available when application calls SQLRowCount. ODBC 3.x applications must either call SQLRowCount to retrieve the result set or SQLMoreResults to cancel it. When an application executes a batch or stored procedure containing multiple INSERT, UPDATE, or DELETE statements, the result set from each modification statement must be processed using SQLRowCount or cancelled using SQLMoreResults. These counts can be cancelled by including a SET NOCOUNT ON statement in the batch or stored procedure.
To Top