server / database stability
-
Hi,
I've been tasked with a rather tricky decision for my company....
We have a sql server cluster at a data centre with 2 main databases on it.
There is an application database and a management information database.
Currently without either one of these working the whole system will not work.
Our developers have quoted a rather large figure to change the code so that if the MI database is down then the application will continue to function.
The question is...is it worth it? Reason being how likely is it for 1 of the 2 database to go down rather than the whole server.
Hope that makes a little sense.
Many thanks
Karl
-
I guess first question is what do you mean by "Not working"? If for some reason the DB goes offline? Hard drive fills? DB closes???
What information is contained in the MI database that is NEEDED to operate the application?
Good Hunting!AJ Ahrens
webmaster@kritter.net -
All of the above
basically anything that causes a failure - is an individual database failure more likely than a server failure etc.It's all down to cost vs reliability.
MI is currently necessary for the application to work.
The change the developers want to expensively put in - is to separate the MI out so it is not necessary at all.
-
Generally a server will go down more often than an individual database. I guess the question boils down to: IF one DB goes down AND it is required to work THEN why not have an alert system built to notify that there is a problem instead of an EXPENSIVE method of removal////
Good Hunting!AJ Ahrens
webmaster@kritter.net -
ok many thanks - thought that was the case - we'll find out quick enough when something dies
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply