Database Reference
In-Depth Information
Planning a new database
Planning a new database can be a daunting task. It's easy to get overwhelmed by it, so here
we present some planning ideas. It's also easy to charge headlong at the task as well, thinking
that the parts you know are all the things you'll ever need to consider.
Getting ready
You are ready. Don't wait to be told what to do. If you haven't been told what the requirements
are, then write down what you think they are, clearly labeling them as "Assumptions" rather
than "Requirements"—we mustn't confuse the two things.
Iterate until you get some agreement, and then build a prototype.
How to do it...
Write a document that covers the following items:
F Database design: Plan your database design.
Calculate the initial database sizing
F Transaction analysis: How will we access the database?
Look at the most frequent access paths
What are the requirements for response times?
F Hardware configuration
Initial performance thoughts—will all data fit into RAM?
F Localization plan
Decide server encoding, locale, and time zone
F Access and security plan
Identify client systems and specify required drivers
Create roles according to a plan for access control
Specify pg_hba.conf
F Maintenance plan: Who will keep it working? How?
F Availability plan: Consider the Availability requirements
checkpoint_timeout
Plan your backup mechanism, and test them
 
Search WWH ::




Custom Search