(PHP 4 >= 4.3.2, PHP 5, PECL odbtp >= 1.1.1)

mssql_free_statementFree statement memory


This function was REMOVED in PHP 7.0.0.

Alternatives to this function include:


mssql_free_statement ( resource $stmt ) : bool

mssql_free_statement() only needs to be called if you are worried about using too much memory while your script is running. All statement memory will automatically be freed when the script ends. You may call mssql_free_statement() with the statement identifier as an argument and the associated statement memory will be freed.

Elenco dei parametri


Statement resource, obtained with mssql_init().

Valori restituiti

Restituisce TRUE in caso di successo, FALSE in caso di fallimento.


Example #1 mssql_free_statement() example

// Create a new statement
$stmt mssql_init('test');

// Bind values here and execute the statement

// once we're done, we clear it from the memory
// using mssql_free_statement like so:

Vedere anche:

  • mssql_bind() - Aggiunge un parametro ad una procedura memorizzata (stored procedure) locale o remota
  • mssql_execute() - Esegue una procedura memorizzata su un database MS SQL
  • mssql_init() - Inizializza una procedura memorizata locale o remota
  • mssql_free_result() - Libera la memoria di un risultato

add a note add a note

User Contributed Notes 1 note

mitch at 1800radiator dot kom
15 years ago
Maybe it's unique to my FreeTDS configuration, but if I don't call mssql_free_statement() after every stored procedure (i.e. mssql_init, mssql_bind, mssql_execute, mssql_fetch_array), all subsequent stored procedures on the same database connection will fail.

I only mention it because this man-page deprecates the use of mssql_free_statement(), saying it's only there for run-time memory concerns.  At least in my case, it's also a crucial step in the process of running a stored procedure.  If anyone else has problems running multiple stored procedures on the same connection, I hope this helps them out.
To Top