Thank You to all for your suggestions.
Thank You Craig Ringer. Your suggestions are very useful to me. Now only, I
am collecting the data so at present I can't say, How much data I expect.
Now I got idea and confident to design my database. Thank you so much.
On Feb 25, 2011, at 6:24 PM, Craig Ringer wrote:
> In reality you must plan periodic updates, in which case it's quite likely
> that the growth of hardware and software performance will keep up with the
> data growth.
I've been in a lovely little niche that has fit that description since 1993 ;
On 24/02/2011 10:59 AM, Kalai R wrote:
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.
Oh yeah, for what it's worth: my employer has 10-year-old
On 24/02/2011 10:59 AM, Kalai R wrote:
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.
What is "too large?"
If you keep PostgreSQL up to date,
On Wed, Feb 23, 2011 at 9:59 PM, Kalai R wrote:
> Is it possible to maintain in a single database for all years of data?
Yes it is possible. But nobody can answer that for your specific
situation without knowing the amount of data and how you plan to use
it.
--
Sent via pgsql-general mailing l
