ODBC - FMTONLY

Hi There

I need to know if the "perform translation for character data" odbc connection option is responsible for SET FMTONLY statements, i think it is but i cannot find 100% confirmation from knowledge base articles or various searches.

Secondly if this option is unchecked will it stop FMTONLY statements completely.

Thirdly if it is enabled, what is responsible for FMTONLY statements not having a where clause ? the odbc driver or the application using the odbc connection, i am sure it is the application but once again , i need confirmation.

Thank YouNo, the two are seperate. 'SET FMTONLY' is used when the driver needs metadata before a statement has been executed. The driver turns FMTONLY OFF as soon as it has the metadata. You can check what's happening with SQL Profiler. The driver uses FMTONLY internally inresponse to some sequences of ODBC calls. An application could also execute SET FMTONLY statements itself. An ODBC trace would show if the application is doing this.|||Hi Chris

That is my issue.Millions of set fmtonly statements are being generated.
So this is directly application related?
My issue is that no FMTONLY statements have where clauses, is this also application responsible?

I have issues where sometimes a FMTONLY statements that normally takes 0 Duration takes 60-90 seconds, if you know about this please check out the TSQL forum for my question.

Do you have a good link or article about ODBC and specifically FTMONLY?

Thank You|||The following looks as though it may be related to your problem

http://support.microsoft.com/kb/836830/

FMTONLY is used by ODBC and OLE DB to get metadata for a query qithout actually executing the query. Sometimes the query would get executed and this would explain the long execution times you are seeing.

What versions of software are you using?

ODBC - FMTONLY

Hi There

I need to know if the "perform translation for character data" odbc connection option is responsible for SET FMTONLY statements, i think it is but i cannot find 100% confirmation from knowledge base articles or various searches.

Secondly if this option is unchecked will it stop FMTONLY statements completely.

Thirdly if it is enabled, what is responsible for FMTONLY statements not having a where clause ? the odbc driver or the application using the odbc connection, i am sure it is the application but once again , i need confirmation.

Thank YouNo, the two are seperate. 'SET FMTONLY' is used when the driver needs metadata before a statement has been executed. The driver turns FMTONLY OFF as soon as it has the metadata. You can check what's happening with SQL Profiler. The driver uses FMTONLY internally inresponse to some sequences of ODBC calls. An application could also execute SET FMTONLY statements itself. An ODBC trace would show if the application is doing this.|||Hi Chris

That is my issue.Millions of set fmtonly statements are being generated.
So this is directly application related?
My issue is that no FMTONLY statements have where clauses, is this also application responsible?

I have issues where sometimes a FMTONLY statements that normally takes 0 Duration takes 60-90 seconds, if you know about this please check out the TSQL forum for my question.

Do you have a good link or article about ODBC and specifically FTMONLY?

Thank You|||The following looks as though it may be related to your problem

http://support.microsoft.com/kb/836830/

FMTONLY is used by ODBC and OLE DB to get metadata for a query qithout actually executing the query. Sometimes the query would get executed and this would explain the long execution times you are seeing.

What versions of software are you using?

Objects in Procedure or Data Cache

I am having some performance issues on my server and wish to track down the particular objects responsible.
Is there any way of determining which objects are in memory?
Many thanks.
Dontable "syscacheobjects" in master database, for cache usage.
setting up a trace in SQL Profiler is also useful

des|||Thanks Des,
It provides some of what I am looking for. I don't seem to find objects of type 'user table' being generated. My SQL Server reports to be using something like 1.4 GB memory from Sysmon. I was hoping that syscacheobjects will shed like on the objects in memory. However, I will continue with the profiler.

Many thanks once more.

Don

Originally posted by DesmondX
table "syscacheobjects" in master database, for cache usage.
setting up a trace in SQL Profiler is also useful

des|||an easy way to keep unnecessary stuff out of memory is to run a scheduled "checkpoint" command on each database every few hours, to flush the memory to disk...

good luck sorting it out...
des