I have inherited a database that is blighted with @DbCommands for retrieving data from Oracle tables. It is causing no ends of performance problems. We actually have an instance of LEI sitting installed and configured not being used and I planned to synchronise all the lookups into Notes documents in a lookup db and remove all instances of ODBC @DbCommands and @DbLookups etc. Anyone got any gotchas/pros or cons before delving into this?
Subject: @DbCommand v LEI
If @DbCommands refer to multiple tables in Oracle, then you gotta pull all those table through LEI to the Notes “lookup db”.You also need to pull “all” records in the tables.
I would say, you go for LEI if number tables are not many. Because for each table one new LEI activity is needed.
If performance is the prime concern, and since you already have LEI up and running, caching the Oracle data is a very good option.
Also, LEI runs as batch job, over midnight/weekly. So there is time period for which teh data in Cache is outdated.
Regards
Litty Joseph