how to do hardware and SW assesment.

hi
if i want to evaluate my database servers and make sure that i am free of risks. i have told to make risk assesment on my databasees or SWs..how ut can be done.
besmile4everAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

CallandorCommented:
Basically, you want to know if you have redundancy in your hardware and software such that if a piece of hardware fails, there is a backup system.  The same is true of a fault in the software.  Make sure your backup plan covers failures and allows you to restore to the point where the business can continue to operate.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
besmile4everAuthor Commented:
hi
ok what about the database it self is there any important parameters that I should take care of it..
0
CallandorCommented:
Keep your log files on a different drive from the data.  There are whole books written on tuning databases for optimal performance, so I won't go into that here.  You do want regular backups of your databases in a rotating schedule so that in the worst case, you only are off by one day's worth of data, so make daily backups, then weekly backups and monthly backups.

You want to make sure no one can freeze your database with exclusive locks on records unless they absolutely need to, and then only for a short time or off hours.  You should have permissions in the database so that no one goes in as sysadmin; give them the minimum amount of permissions to enable them to do their job.  Guard against queries that return an excessive number of records; these can crash a server or prevent anyone else from using the database.  Perform periodic load balancing if you have the option to keep one machine from being overwhelmed.
0
besmile4everAuthor Commented:
thanks.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Databases

From novice to tech pro — start learning today.