ODBC tracing! No Info

Hi I know I should be able to find this out myself , but both book I have don't seem to know and the online helps isn't much better.

I want to find out if ODBC tracing is on or off, and if it is on I want to be able to turn it off.

How can I do this? I just can't find any Info on it!

Thanks Ed

P.S. If their was a Icon for simpleton, I would use it!ODBC Tracing? I'm not sure what you are talking about. You can get server and connection information with these commands:

sp_configure
SQLGetConnectAttr
SQLSetConnectAttr

blindman|||Originally posted by blindman
ODBC Tracing? I'm not sure what you are talking about. You can get server and connection information with these commands:

sp_configure
SQLGetConnectAttr
SQLSetConnectAttr

blindman



My orginal problem was that EM runs really slowely when looking a propeties. So I searched through the existing threads to try and find out what the problem and one of the suggestion was that I may have ODBC tracing turned on and that could be slowing down the system, but I could not find a way see if ODBC tracing was on or off.

I thought it was on a setting withine the database , now figured it out by talking to the other in the office, sorry, thanks anyway!|||odbc tracing is in admin tools/datasource configuration. it comes very handy by allowing to see what actual statements are issued by the driver manager. poobah probably never used it :)|||Nope. I haven't. My expertise is in database design, transact sql programming, and query optimization. I know a fair amount about database tuning and administration, but in general I leave those posts to others to answer.

Like nixies, I couldn't find anything in Books Online referencing this configuration. Is it strictly middle-tier or interface resident?

blindman|||all sql server client tools are using odbc driver manager one way or the other. below is a sample set of entries from the log file if you turn tracing on in your data sources tracing tab:

SQL Server Ente 7b4-794 ENTER SQLAllocHandle
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 00000000
SQLHANDLE * 01B471D4

SQL Server Ente 7b4-794 EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 00000000
SQLHANDLE * 0x01B471D4 ( 0x01a31540)

SQL Server Ente 7b4-794 ENTER SQLSetEnvAttr
SQLHENV 01A31540
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 0x00000003
SQLINTEGER -5

if tracing is turned on the performance of that workstation deteriorates. as an example i turned it on and opened em and expanded a server (in a sense connected to it). within a minute after it i turned tracing off. the resulting file size was 472K. mind you i didn't do anything other than what i described, - connected to the server and nothing else.|||Now I see. So its a workstation setting, not a server setting.

Thanks

blindman|||not necessarily, you can do the same thing on the server.

ODBC Tracing

What is ODBC tracing?
You mean from the ODBC Data Source Administrator? That will
caputure ODBC function calls and their success or failure
and write it out to a text file on the client where tracing
is enabled. It takes a toll on the machine and will slow
things down so you really only want to use it for brief
troubleshooting periods and then turn it back off.
-Sue
On Wed, 10 Aug 2005 16:22:07 -0700, "docsql"
<docsql@.noemail.nospam> wrote:

>What is ODBC tracing?
>

ODBC Tracing

What is ODBC tracing?You mean from the ODBC Data Source Administrator? That will
caputure ODBC function calls and their success or failure
and write it out to a text file on the client where tracing
is enabled. It takes a toll on the machine and will slow
things down so you really only want to use it for brief
troubleshooting periods and then turn it back off.
-Sue
On Wed, 10 Aug 2005 16:22:07 -0700, "docsql"
<docsql@.noemail.nospam> wrote:

>What is ODBC tracing?
>

Odbc trace

Hi

I run odbc trace , thru ODBC Adliministrator > Tracing tab.

Is there a way to have the trace of

sql_parm_input, sql_c_wchar, sql_varchar of sqlbindparameter

For exmple :

MSACCESS 698-548 ENTER SQLBindParameter
HSTMT 07CD24F8
UWORD 1
SWORD 1 <SQL_PARAM_INPUT>
SWORD -8 <SQL_C_WCHAR>
SWORD 12 <SQL_VARCHAR>
SQLULEN 36
SWORD 0
PTR 0x67184BD4
SQLLEN 0
SQLLEN * 0x67184BD0

Thanks

Seems that odbcspy is doing the job ,

Found that odbcspy come with mdac sdk 2.0, but cannot find it

does anybody where can I download IT ?

|||

You can get the latest MDAC SDK from:

http://www.microsoft.com/downloads/details.aspx?familyid=5067faf8-0db4-429a-b502-de4329c8c850&displaylang=en

You could also search the http://www.microsoft.com website for "MDAC SDK".

ODBC SQLINTEGER & (BADMEM) - Why?

Hi,
I have the ODBC tracing enabled on my development machine using the
"default" tracing DLL.
I thought it was just our applications causing this, but I'm also seeing
this when using isqlw (SQL Query Analyzer).
Is it an issue? The app. seems to have no issues. I know it is indicating
that the memory location is invalid. Why?
I would like to know what the cause is, what other tools are available to
track this down, in the event it is an issue. It doesn't seem like a
"normal" occurrence.
From our app:
12345678.A24 N 95c-cdcEXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS)
SQLHENV 008F1540
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 0x00000003 (BADMEM)
SQLINTEGER 0
12345678.A24 N 95c-cdcEXIT SQLSetConnectAttr with return code 0
(SQL_SUCCESS)
SQLHDBC 008F15E8
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 0x0000003C (BADMEM)
SQLINTEGER 0
From ISQLW:
isqlw edc-9c4EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS)
SQLHENV 008D1540
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 0x00000003 (BADMEM)
SQLINTEGER -5
isqlw edc-9c4EXIT SQLSetConnectAttrW with return code 0
(SQL_SUCCESS)
SQLHDBC 008D15E8
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 0x0000000F (BADMEM)
SQLINTEGER -5
isqlw edc-9c4EXIT SQLSetStmtAttrW with return code 0
(SQL_SUCCESS)
SQLHSTMT 008D19B8
SQLINTEGER 3 <SQL_ATTR_MAX_LENGTH>
SQLPOINTER 0x0000FC00 (BADMEM)
SQLINTEGER -5
Thanks. Jeff
Hello,
This behavior seems to be normal because some parameters are not used when
calling this method. Also, the SQL_SUCCESS indicate these functions work
fine. For example:
SQLSetConnectAttr Function
http://msdn.microsoft.com/library/de...us/odbc/htm/od
bcsqlsetconnectattr.asp
ValuePtr
[Input]
Pointer to the value to be associated with Attribute. Depending on the
value of Attribute, ValuePtr will be a 32-bit unsigned integer value or
will point to a null-terminated character string. Note that if the
Attribute argument is a driver-specific value, the value in ValuePtr may be
a signed integer.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

ODBC SQLINTEGER & (BADMEM) - Why?

Hi,
I have the ODBC tracing enabled on my development machine using the
"default" tracing DLL.
I thought it was just our applications causing this, but I'm also seeing
this when using isqlw (SQL Query Analyzer).
Is it an issue? The app. seems to have no issues. I know it is indicating
that the memory location is invalid. Why?
I would like to know what the cause is, what other tools are available to
track this down, in the event it is an issue. It doesn't seem like a
"normal" occurrence.
From our app:
12345678.A24 N 95c-cdc EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS
)
SQLHENV 008F1540
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 0x00000003 (BADMEM)
SQLINTEGER 0
12345678.A24 N 95c-cdc EXIT SQLSetConnectAttr with return code 0
(SQL_SUCCESS)
SQLHDBC 008F15E8
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 0x0000003C (BADMEM)
SQLINTEGER 0
From ISQLW:
isqlw edc-9c4 EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS
)
SQLHENV 008D1540
SQLINTEGER 200 <SQL_ATTR_ODBC_VERSION>
SQLPOINTER 0x00000003 (BADMEM)
SQLINTEGER -5
isqlw edc-9c4 EXIT SQLSetConnectAttrW with return code 0
(SQL_SUCCESS)
SQLHDBC 008D15E8
SQLINTEGER 103 <SQL_ATTR_LOGIN_TIMEOUT>
SQLPOINTER 0x0000000F (BADMEM)
SQLINTEGER -5
isqlw edc-9c4 EXIT SQLSetStmtAttrW with return code 0
(SQL_SUCCESS)
SQLHSTMT 008D19B8
SQLINTEGER 3 <SQL_ATTR_MAX_LENGTH>
SQLPOINTER 0x0000FC00 (BADMEM)
SQLINTEGER -5
Thanks. JeffHello,
This behavior seems to be normal because some parameters are not used when
calling this method. Also, the SQL_SUCCESS indicate these functions work
fine. For example:
SQLSetConnectAttr Function
http://msdn.microsoft.com/library/d...-us/odbc/htm/od
bcsqlsetconnectattr.asp
ValuePtr
[Input]
Pointer to the value to be associated with Attribute. Depending on the
value of Attribute, ValuePtr will be a 32-bit unsigned integer value or
will point to a null-terminated character string. Note that if the
Attribute argument is a driver-specific value, the value in ValuePtr may be
a signed integer.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.