Re: multi-tenant issues with stored procedures

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 11/28/2017
03:57:19 PM:

We extended this to our stored procedures by passing a "tenant" id as

the

first parameter ... What this switching process does is to replace

the

current job's library list...

What was the rationale for having called stored procedures change the

Job's

library list, rather than having external applications specify the Job's
library list in a connection string property provided by ODBC and JDBC
drivers?

One reason is that the off-platform callers don't know when
library list changes need to be made. Besides which, our philosophy here
is that such environmental issues need to be maintained close to the
source rather than requiring each caller to have intimate details about
how the environment needs to be set up.

Another reason is that in our situation we don't have "tenants"
but have "companies" for which we perform services and for which we have
partial ownership. For financial reporting purposes these companies need
to be rolled up into multiple levels and, eventually, to a single
"corporate" level. Thus, sometimes a process needs to be run across
multiple companies. It is more efficient to perform this cross-company
processing in a single call from off-platform rather than requiring
multiple off-platform calls in order to process each company.


Sincerely,

Dave Clark