Great! Im glad to know
A practice suggestion:
In ADOPREOPENTHRESHOLD() not only the size in records should work as a filter. Also a substring (or a array with substrings) of the tablename are interesting for filtering the DBs for pre-open! (ex. only "2015" -> DB2015 and Faw2015gt and Klima2015 and ......)
Note taken Ill see what can be done.
Could you share your experience ?
Time of conversion of the app
Any app code changed ? Why?
Db engine used
Database size
Average table size (nr of rows)
Biggest table size (nr of rows)
Lan and / or Wan
Nr of users
Concurrent use (new additions by others) and locking
Does app use ?
Relations
Scopes
Filters
Indexes with UDFs
Locks
Transactions
do you use ado or sql directly through for example adofuncs.prg or any class and does adordd catch well eventually new additions by those processes?
Overall performance compared to others rdds 1 to 5 (1 being the slowest)
Is it in production?
Thanks