That is a very well reasoned argument!
I agree! That is what I will do.
Thanks all for your input!
Managing hardware has never been my strong-suit.
Working with hardware and managing the hardware, for me, is like working on
a car...I've done it way more than I ever wanted to, but it is not something
I ever willingly do.
Thanks!
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Evan Harris
Sent: Monday, January 14, 2013 12:54 PM
To: Midrange Systems Technical Discussion
Subject: Re: Storage Size for Programmer
Hi Shannon
I'll go out on a limb and say that it's not my practise to *limit* the
storage of individual programmers, but instead I prefer to manage the system
storage effectively. That includes *managing* the storage used by
individuals but I generally try and avoid explicitly limiting it.
I would certainly collect and report storage by user profile on a weekly or
at least monthly basis and if possible track growth in storage by
individual. But my management efforts would be directed at preventing a
storage overflow by having some kind of monitoring to alert when the storage
reached a threshold (say 95%) and setting the system storage lower limit to
shut the system down to a restricted state to prevent a hard overflow. I
might have the system value slightly wrong as I am working on memory.
My experience over the last few years has been that (for example) temporary
storage for SQL and journal receivers not being cleaned up has consumed more
storage ans threatened availability more than individual developers writing
large files or tables.
I view the storage as an asset so if someone needs to use it temporarily and
it is not already being used I don't have a problem with it. Over the longer
haul I've spent more time arguing about appropriate limits and if people
should be allowed more storage (they always get it) than I ever did managing
overflows caused by an individual going crazy or being careless, though that
has also happened occasionally (not for a very long time).
At the end of the day the approach you choose should reflect the actual
storage available to you on the system, It is quite a bit harder (but not
impossible) to fill a system up these days and the time between being warned
and a critical point being reached is a bit more comfortable than back when
systems were much smaller.
On Sat, Jan 12, 2013 at 7:56 PM, Shannon ODonnell
<sodonnell@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi,
What is a good, average, storage limit to set for a programmer on
their user profile?
I am setting up some user profiles for new developers and I want to
give them a limit on the amount of storage they can use.
I can and probably will adjust that amount over time but I want to
prevent anyone from creating giant databases or user spaces, and such.
Thanks in advance for all suggestions!
Shannon O'Donnell
midrange.com
