The forum will experience an outage sometime between February 10 at 7:00pm EST and February 12 at 11:59 EST for installation of security updates. The actual time and duration of the outage are unknown but attempts will be made to minimize the downtime. We apologize for any inconvenience.

How do I open and operating and save the client software passed the query in order to track!

asked 17 Sep '13, 11:36

mfkpie8's gravatar image

accept rate: 10%

I think you are asking for a way to see what queries the client sends to the server?

If this is correct then you should take a look at Request Logging in the documentation. To get started, add

-zr all -zo somefile.txt

to your server command line, then run your client application, and when done shutdown your server and take a look at the contents of somefile.txt.

You could also use Diagnostic Tracing if you are using SQLA 16.

If your client interface is ODBC on Windows then you could just turn on ODBC's TRACING capability.


permanent link

answered 17 Sep '13, 12:14

Mark%20Culp's gravatar image

Mark Culp
accept rate: 40%

edited 17 Sep '13, 12:16


To answer confusion with certainty the Jedi way this is not, in this forum a danger there is of losing what sanity remains :)

(17 Sep '13, 14:57) Breck Carter
Replies hidden

I'd say Mark's semantical analysis of this question is way beyond my abilities (and my willingness):)

(17 Sep '13, 15:27) Volker Barth

Be a badge for posting a question written like Yoda speaks, there should. Hmmmmmm. - translated by Google

(17 Sep '13, 15:40) Breck Carter

To add to Mark's request logging suggestions, here some SQL that may do the trick :

-- connect to the datbase with dbisql and run -- to start request logging for all connections

CALL dbo.sa_server_option( 'RequestFilterConn', -1 );

CALL dbo.sa_server_option( 'RequestFilterDB', -1 );

CALL dbo.sa_server_option( 'RequestLogFile', 'C:UsersPublicDocumentsreq.log' );

CALL dbo.sa_server_option( 'RequestLogNumFiles', 0 );

CALL dbo.sa_server_option( 'RequestLogging', 'all' );

-- run your application .. e.g..

select * from sysobjects;

-- stop request logging

CALL dbo.sa_server_option( 'RequestFilterConn', -1 );

CALL dbo.sa_server_option( 'RequestFilterDB', -1 );

CALL dbo.sa_server_option( 'RequestLogging', 'none' );

CALL dbo.sa_server_option( 'RequestFilterConn', -1 );

CALL dbo.sa_server_option( 'RequestFilterDB', -1 );

CALL dbo.sa_server_option( 'RequestLogFile', '' );

-- import request log file into global temp tables for analysis

call sa_get_request_times('C:UsersPublicDocumentsreq.log');

call sa_get_request_profile('C:UsersPublicDocumentsreq.log');

-- review request log order by the the time it took

select * From satmp_request_time order by millisecs desc;

-- see if there was any blocking

select * From satmp_request_block;

-- list host variables

select * from satmp_request_hostvar;

-- also check aggregate view on queries with their averages etc..

select * From satmp_request_profile;

(18 Sep '13, 09:15) Lucjan
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 17 Sep '13, 11:36

question was seen: 543 times

last updated: 18 Sep '13, 09:17