Solved

PostgreSQL database design for a large company

Posted on 2011-02-23
3
444 Views
Last Modified: 2012-05-11
We are going to design database for a large company with multi branches. I am using PostgreSQL

For example,

I create a single database for all branches. After 10 years, database size is too large.
I want to know ,at that time, the performance of the database is reduced or not.

Is it possible to maintain in a single database for all years of data?


0
Comment
Question by:gloier
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 7

Accepted Solution

by:
MrNed earned 334 total points
ID: 34966884
When considering single versus multiple databases think about what your requirements for backups, reporting, syncronisation, hosting etc. Personally I would lean towards a single larger database in any situation, any newer versions of PostgreSQL are getting better at handling larger databases.

Do you have any forecasts regarding data volumes, rate of growth etc?
0
 
LVL 62

Assisted Solution

by:gheist
gheist earned 166 total points
ID: 34979948
It is important to know what clients you are using.
i.e JDBC, ODBC, ADO, PHP or all

I would propose slony for two or more slony-replicated databases.
Then you can backup slave database without any influence on master.

You need to do some database housekeeping every week or so. Classically it is vacuuming, but since that happens now automatically you might need to massively delete e.g connection logs etc.

If you use JDBC and C-JDBC you just run as many independent database servers as needed and C-JDBC driver sends updates to all and balances queries for better performance. Similar facilities are achievable with PHP and others.
0
 
LVL 7

Assisted Solution

by:MrNed
MrNed earned 334 total points
ID: 34985446
If you implement any replication such as slony/pgpool make sure you understand their limitations and the complexities involved.

And FYI, trying to design your system to still be viable in 10 years time is extremely optimistic :)
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Never store passwords in plain text or just their hash: it seems a no-brainier, but there are still plenty of people doing that. I present the why and how on this subject, offering my own real life solution that you can implement right away, bringin…
A Stored Procedure in Microsoft SQL Server is a powerful feature that it can be used to execute the Data Manipulation Language (DML) or Data Definition Language (DDL). Depending on business requirements, a single Stored Procedure can return differe…
Steps to create a PostgreSQL RDS instance in the Amazon cloud. We will cover some of the default settings and show how to connect to the instance once it is up and running.
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question