RE: Normalization was Left AS/400 and Returned

Normally the number of database changes are small.  But when we do things 
like upgrade BPCS, or save/restore a library to a different name for a new 
division we do have to scramble to update queries.  However we insist that 
all queries for each division be in a specific library.  Not in any 
individual user libraries.  We do even have a utility that will tell us 
which Query's touch a particular file.

The users are going to generate their own queries.  If we insisted on a 
strictly programmer controlled access via stored procedures, etc, then 
what would happen but the users insisting on us duplicating all data to a 
PC so that they can run their own queries against it.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/05/2005 09:23 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Normalization was Left AS/400 and Returned






> From: Fisher, Don
> 
> I keep reading about the benefits of stored procedures on this list
and
> intend to explore their possibilities at some point.  For the present,
I
> and
> my colleagues have more pressing issues.  That's what happens when a
> development staff is half the size it needs to be.  The good news is
that
> if
> we need to make a database change, we do and notify the "power" users
of
> that change so they can make appropriate modifications to their
queries.

And this works fine as long as the number of queries and the number of
database changes is small.  But remember, the idea behind letting power
users do their own queries is to save them time, right?  Well, the first
time you make a database change that affects more than a couple of
queries, I guarantee you will get some pushback from your power users.
And maybe that's the point at which you review your policy and move to a
stored procedure environment; the problem often being that by that time
the power users have such an investment in the old approach that any
conversion will face massive resistance.

(And I agree that the upload, edit, post cycle for data from
spreadsheets is perfectly acceptable and a good way to get external
data, whatever the source, into the system.)

Joe

-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.