dorelse
Member
Registered: Apr 2001
Location: Des Moines, IA
Posts: 248 |
Well, in an ideal situation, you're absolutely right! Network shares are the way to go, now, i would argue that 500k in relation to today's disk capacities (or even 5MB) isn't such a big concern.
I'm a DBA for a HUGE Ins company...we're talking terabytes of information on a sysplex IBM z-series boxes. So from my perspective 5MB is small potatoes...again is relative.
However, we use Outlook as well, and I can tell you that both network shars are use, and also not used. Multiple copies of attachments fly by with edits, comments, etc, etc. I'm sure that this frustrates our Exchange/Outlook team.
However, I'd argue this...as a Network Admin, (and in my case a DBA), our jobs are to support & provide an infrastructure for our users to accomplish their goals in the best, fastest, and most effective way possible so they can maximize their time & energy on generating income for the company.
You'd probably argue that disk space will cost the company money, and it will...but disk space is relatively cheap. I could see you saying that anything over 1MB should be on a share, but that really is a decision that your users need to decide on a case by case basis...what's the most effective solution for this attachement...network share, or e-mail attachment. I know we don't have any limit here, we're asked to use our brains and figure out what makes the most sense.
I do know that our friendly Exchange server team will give us a call if something falls on their radar screens.
Also, this is somewhat managed by only allowing us like 300MB of storage per user on the server...so we can't store everything forever. And we can ask them to burn a CD for us if were about to lose something we desperately need...but that's when they'll say, "Well, how about moving it to a network share?".
A real world example for you...we currently have in our Database 3 separate copies of a 20+ Million row table. Why? It doesn't make sense on the surface, its takes up a lot of disk space, drove the Storage Admin guys crazy. Until we showed them the Business case as to why its needed. We needed it for 3 reasons..its a tremendously important table to our company contanining vital customer info. It was getting hammered by all the people needing access to it, to the point that its performance was making it unusable for all.
We discovered that not everyone needed the up-to-date information, so we created a copy, added a nightly update process to it, and then migrated a bunch of data off to a history table, even though its still contained in the 'current' table.
The data's all over the place, but the desire for a nice clean 3rd Normal Form database is completely overridden by the business's need to accomplish its work/goals/etc, in the most timely and efficient manner possible. Is my life more difficult managing the database, absolutely...but that a small price for the user's gratitude in finding a solution that makes them happy, and got the system response time back to a useable state.
In other words, you're there to support & guide their efforts, not hinder them...if they want attachments flying all over the place, show them the cost of all the dasd they'll be buying...put it into $$$ and then they can decide what's right for them....
|