Re: multi-tenant issues with stored procedures -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: multi-tenant issues with stored procedures
From: Buck Calabro <kc2hiz@xxxxxxxxx>
Date: Wed, 29 Nov 2017 17:10:59 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 11/29/2017 4:26 PM, Nathan Andelin wrote:

On Wed, Nov 29, 2017 at 2:15 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

I'm not running a multi-tenant setup, but I do have test and production
environments.

Buck, are you using the setup that Evan referred to in his first link?

No. Our volumes are too low to set up a separate subsystem (memory
pool, etc) for this subset of the workload.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: multi-tenant issues with stored procedures , Nathan Andelin

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.