[unisog] "Enterprise" SQL-based applications.
Michael.Janke at csu.mnscu.edu
Tue Dec 7 14:03:52 GMT 2004
This would be very useful. We typically run into vendor FUD when we
mention the possiblity of running more than one app on a server.
We'd include a specification such as this in RFP's.
Director, Network Services
Minnesota State Colleges and Universities
1450 Energy Park Drive Suite 300
St Paul MN 55108
>>> derek.ethier at humber.ca 12/06/04 9:24 AM >>>
I have come across a particular situation a number of times and I was
if anyone had some innovative way of handling it.
Due to the fact that we are an "Enterprise" (ugh, I hate that term
environment quite often I recommend using Enterprise applications (or
of..) that routinely require SQL-based services (commonly, MS-SQL).
many of these applications are developed with much smaller organizations
mind and naturally assume that they are the only application using a
SQL instance. Through this assumption they routinely require sa (or
access, changes to the master database (embedded owner privileges on
my!), etc. or the application will not work.
Rather than spend $$ on many different database servers (licensing,
etc.) I would like to come up with a standards' type document that
a truly "Enterprise" SQL-based application really is, and what a
should expect when dealing with an Enterprise environment (particularly
Has anyone drawn anything like this up before? If so, is it useful? Is
I'm proposing useful?
Any information would be appreciated. Thanks.
unisog mailing list
unisog at lists.sans.org
More information about the unisog