There is a resource leak in ULIndexSchema that is being used by DataTable. This leak is generally seen if you are using DataTables multiple times in an application instance with the same database connection. The same issue exists if the application is directly using ULIndexSchema. Overtime, the SQLE_TOO_MANY_TEMP_TABLE error will be encountered if the connection is not closed. A fix is currently being investigated for v12 and later that will provide a method to release the resources used by ULIndexSchema.

A workaround is to isolate the connection used by the DataTable and release it as soon as the DataTable is no longer being used. For example, this code should avoid this issue:

    ULConnection conn =  new ULConnection( conn_parms );
    DataTable dt = new DataTable();
    ULCommand qry = new ULCommand( a_sql_qry, conn );
    ULDataReader dr = qry.ExecuteReader();
    dt.Load( dr );
    \*...application use of DataTable ... *\
    dr.Dispose();
    dt.Dispose();
    qry.Dispose();
    conn.Close();

Since it is happening randomly, it is unlikely the result of one overly complicated query.

Frequently this is the result of not properly closing result sets. Review your code to ensure database resources are released in a timely manner and reduce the number of simultaneously open cursors you have.

We're a PB shop. Our app uses ASA (started with 7 currently using 16). we learned long ago to do a COMMIT after select statements to unlock rows and close cursors. I'm not sure if a COMMIT in an UltraLite db will do the same.