URGENT: Error 5701

[Naimps]

Hi.

Does anybody know what means this, and how to solve it?

[Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to
'master'.

[Andy Cohen]

5701 should not be considered an error. Instead, it's just an informational
message that tells your application which database it is currently using.
This information will be useful to some applications, and should be ignored
by all others.

Let me know if you need more information,

Andy Cohen
aco...@tildenpark.com
www.tildenpark.com

[Rafael Sanchez Martinez]

If you go to the "SQL Server Books Online", you'll find this:

"Severity Level 0

Message Text
Changed database context to '%.*s'.

Explanation
This is an informational message indicating that the CHECKUPG.EXE utility
has changed the current database context to the master database. (It has
essentially executed a USE master statement.)
Action
None needed"

(This source of information says Severity = 0, but is actually severity 10)

This means that during your connection, the default database has changed to
"master". Any time you change the default database, you receive a message
like this.

Actually, this is not an error; in your error trap, you need to filter the
messages that you receive from SQL by severity, if you don't want things
like this to pop-up in your applications.

In SQL Enterprise Manager, Server|Messages... where you'll find all the SQL
messages clasified by severity.

Hope this will help.

Rafael Sanchez

Naimps wrote in message <6sh1ms$749$1...@talia.mad.ibernet.es>...

[Naimps]

Thanks for your help, but I have a question: the messages filtering is done
by my aplication, not in SQLServer, isn't it?

I looked for ODBC SDK 3.5 reference and I have found SQLSetConnectAttr
function with the SQL_ATTR_CURRENT_CATALOG attribute. Is it right?

Another question:

>This is an informational message indicating that the CHECKUPG.EXE utility
has changed the current database context to the master database. (It has
essentially executed a USE master statement.)

What is "USE master statement"?

Thank you very much.

[Andy Cohen]

Naimps wrote in message <6t03kf$2qv$1...@talia.mad.ibernet.es>...

>Thanks for your help, but I have a question: the messages filtering is done
>by my aplication, not in SQLServer, isn't it?

Yes, that's right.

>
>I looked for ODBC SDK 3.5 reference and I have found SQLSetConnectAttr
>function with the SQL_ATTR_CURRENT_CATALOG attribute. Is it right?

Yes, that call sets the current catalog of the connection, and will cause
another 5701 message to be generated.

>
>Another question:
>>This is an informational message indicating that the CHECKUPG.EXE utility
>has changed the current database context to the master database. (It has
>essentially executed a USE master statement.)
>
>What is "USE master statement"?

Let me re-arrange the quotes to make the answer clearer:

It has essentially executed a "USE master" statement.

In SQL Server (Sybase or Microsoft), the USE statement tells the current
connection to change its current catalog. In this case, the statement is
telling the connection to use the "master" catalog (sometimes called the
"master" database).

>
>Thank you very much.
>
>

I hope this helps,

Andy Cohen
aco...@tildenpark.com
www.tildenpark.com