Stick to basic db design principles. ONE table for ONE domain. One
transaction table. Scrap the idea of one per month.

If the database does not scale to this, get one that does.

Thomas

> -----Original Message-----
> From: firebird-support@yahoogroups.com
> [mailto:firebird-support@yahoogroups.com] On Behalf Of
> women_lover_best
> Sent: Mittwoch, 20. Juli 2005 08:24
> To: firebird-support@yahoogroups.com
> Subject: [firebird-support] Design guidance
>
> We are developing a POS application..on average there will be
> 50-60 terminals connecting to server..and there will be many
> transactions in day(guess 1 to 2 lakh)..now should i make my
> transaction table for each month..which means there will be
> 12 tables..or is there any other way..i am thinking from
> performance and management..and reports..
> thks
>
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://firebird.sourceforge.net and click the Resources
> item on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Yahoo! Groups Links
>
>
>
>
>
>
>