Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
lemondash
Posting Yak Master
159 Posts |
 Posted - 2009-03-23 : 13:08:08
|
| Afternoon all,Not too sure where to place this message. But basically what has happen I’m working for company that has a fairly comprehensive and large Database.Since working for this company have notice certain things that are not correctly config, can I also see basic bad database design and on top of that there are other things that I believe in my experience that are wrong.It’s all good I telling others in the company my ideas, but they want me to document it, so that it can be turned in to project and also for costs justifaction. Now I have never had to do this sort of documentation before. I have no idea for a starting pointDoes anybody know where i could get a template from to get me started?Or just any help would be great? |
|
|
elancaster
A very urgent SQL Yakette
1208 Posts |
Posted - 2009-03-24 : 03:58:59
|
| you will not find... nor do you need a template. it's not about what the doc looks like, its about how clearly you argue your case.you need to write down all the things you feel are wrong, evidence them as to why you think they are wrong, suggest a solution or solutions for each point and try and consider timescales / resource / disruption of service etc. they are all questions that will need to be addressed. and unfortunately we cannot really help you with that as only you know your systemsEm |
 |
|
|
darkdusky
Aged Yak Warrior
591 Posts |
Posted - 2009-03-24 : 06:07:26
|
| I agree with elancaster.Good database design by definition has benefits because the "rules" were developed to maintain data integrity, security and optimise performance.List each case where you see something wrong, put them into categories, e.g. Performance, Security, Integrity, etc. State the benefit from any change, how long it will take and it's cost if any. Also give the cost of not making change, e.g. "increased chance of data loss" etc.If you can't find a template to describe what is wrong - there are plenty for good design practice - use one to identify your system's failures.Things to look at in no particular order:primary keys, indexes, sql user permissions, windows permissions on servers, backups, recovery plan in case of disaster, normalisation, password policy, firewall, vulnerability to sql injection from webpages, etc. |
|
|
|
|
|
|
|
|
help needed