What is temporary table instancing?
Instancing in the application engine context is when a process run by the user is assigned a dedicated temporary table.
When should it be used?
It’s a must when there are multiple users running the same process concurrently, or when the same user is running the same process concurrently (i.e. multiple times in parallel).
How does it work?
A new table is created in the database with a number suffix that represents the instance number. So for example, if a user runs the SCC_3CD_PMGR process, the system will create a dedicated temporary table called SCC_3CD_TMP2. This table is locked specifically for that process, and will only be released when the process is completed successfully. If another user decides to run the SCC_3CD_PMGR process at the same time, that user will be assigned a new dedicated temporary table called SCC_3CD_TMP3. Having a dedicated temporary table eliminates the burden of resource contention – when a process has to wait for another process to unlock the table or a row in the table.
What are the benefits of instancing?
Instancing will improve performance if you’re sure that multiple users will be running the same process concurrently or the same user will be running the same process concurrently. Users can do this by opening up the application engine in Application Designer and then changing the instance count (click the Properties button and then the Temp Tables tab).