Re: mssql_execute(): stored procedure execution failed

Context change messages are severity level 10. I usually set my severity
level to 16 (anything higher and you are shutting up real messages - 1-16
are status messages).

If you changed your severity levels to 16 and you still get that notice then
I have to suspect that PHP is not reading your ini file properly. Are you
changing it in the ini, or with a call to
mssql_min_error_severity()/mssql_min_message_severity()?

On Thu, May 27, 2010 at 2:40 AM, Sylvain Viart - Gmail <
[email protected]> wrote:

> Hi,
>
> On 24/05/2010 18:27, Robert Gonzalez wrote:
> > mssql_init() essentially prepares a stored proc to be called as a
> prepared
> > statement with the possibility of placeholders added to it for multiple
> > calls using different params. mssql_bind() allows you to bind those
> > different params into the prepared statement for processing using the
> > mssql_execute() function.
> >
> > mssql_query() takes the query as entered, sends it to the database server
> > and receives the response from the DB server, usually in the form of a
> > result resource handle. You can just as easily send stored procedure
> > requests using mssql_query() as you could using init, bind and execute.
> Thanks.
>
> mssql_get_last_message() give useless message. :-(
>
> I've tried to raise the error severity from 10, 16, 17
>
> ; Minimum error severity to display.
> mssql.min_error_severity = 17
>
> ; Minimum message severity to display.
> mssql.min_message_severity = 17
>
>
> no change.
>
> here is the error message:
>
> Changed database context to 'D2_master'.
>
> where D2_master is the database name.
>
> Still searching.
>
> Regards,
> Sylvain.
> _______________________________________________
> FreeTDS mailing list
> [email protected]
> http://lists.ibiblio.org/mailman/listinfo/freetds
>



-- 
Robert Gonzalez
http://www.robert-gonzalez.com
http://twitter.com/RobertGonzalez
http://www.linkedin.com/in/robertanthonygonzalez