Jump to content
Sign in to follow this  
Larry Hengen

FireDAC calling sp_pkeys

Recommended Posts

I am using an old version of FireDAC (Berlin time frame) and when opening an updateable query it implicitly calls sp_pkeys which can take ~1.5s to return.  It seems to do so only once and then caches the PK info for the table appearing in the SQL FROM clause.  Grepping the source has yielded no information, and my Google fu is failing me. Depending on the use case, this sometimes results in poor performance.  For instance if the user fires up the app and goes into a screen to update some data and then closes the app, they trigger all of the metadata queries during their usage.  Over slower VPN connections this can be a real problem.  It would be nice to be able to prevent FireDAC from making such a metadata call.  Can we specify the PK column at design-time or run-time and prevent the metadata query?  After all the database PKs seldom change.

Share this post

Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this