November 26, 2017 at 11:36 am
Hello experts,
A developer is seeing an error like the following, and can't seem to pinpoint the errors in order to stop them.
I am having trouble creating a trace that captures either the error culprit itself, the error message being sent, or even the attempted USE DATABASE command that I presume would be sent in order before this kind of error is triggered.
[256] Invalid query: Unable to connect to database Changed database context to Foo
Does anyone know what kinds of SQL Trace event classes and/or filters I could use? I have tried the Errors and Warnings events such as Attention, Execution Warnings, and User Error Message without retrieving anything useful so far. Not sure if this is relevant, but the connection is coming from PHP to SQL 2016.
Thanks for any help. Let me know if there's any other information I could provide that might help.
- webrunner
-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html
November 28, 2017 at 7:24 am
webrunner - Sunday, November 26, 2017 11:36 AMHell experts,A developer is seeing an error like the following, and can't seem to pinpoint the errors in order to stop them.
I am having trouble creating a trace that captures either the error culprit itself, the error message being sent, or even the attempted USE DATABASE command that I presume would be sent in order before this kind of error is triggered.
[256] Invalid query: Unable to connect to database Changed database context to Foo
Does anyone know what kinds of SQL Trace event classes and/or filters I could use? I have tried the Errors and Warnings events such as Attention, Execution Warnings, and User Error Message without retrieving anything useful so far. Not sure if this is relevant, but the connection is coming from PHP to SQL 2016.
Thanks for any help. Let me know if there's any other information I could provide that might help.
- webrunner
User Error Messages would pick up errors sent back to the client. It is possible that the error is not coming from SQL Server.
If you weren't able to capture anything it is also possible the developer is pointing to some other server/database than the one you are tracing. I don't remember seeing that error with SQL Server and that error number is associated with a different message in SQL Server.
Sue
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply