I was reported by a load-test team of one client project.
They said two many function call requested by ArcSOC.exe. and to improve performance of sql query, should modify function call to raw sql statements.
they gave me the function-call sql like SDE.ST_EnvIntersects.
I want to check two things.
- Using function call, is more load on DB, than sql query.
- If yes, How to reduce internal function call?
A. reduce returned features.
- to fetch versioning data , require bigger function call than non-versioning data?
(I see delta tables query in sql scanning)
The SDE.ST_EnvIntersects function is the least-intensive spatial query constraint. There is no raw SQL replacement (unless you disable spatial queries with attribute-first, which would be much more intensive).
Versioned queries are, of course, more intensive than non-versioned queries (due to the UNION ALL join).
Thank you for your response.
We deep concern whether remove versioned data.
That is certainly your choice, though versioning is the only way to accomplish long transaction editing in Desktop and ArcGIS replication.