seperating into a number of databases
From: danjourno <danjourno_at_hotmail.com>
Date: Sat, 4 Jan 2003 16:30:18 +1100
Message-ID: <3e167179$0$7817$afc38c87_at_news.optusnet.com.au>
I am building a website that is based on members, and I am developing an affiliate system for it.
where people can refer others to my site via a link from theirs. This system will also store information on any monetary transactions that are made.
Date: Sat, 4 Jan 2003 16:30:18 +1100
Message-ID: <3e167179$0$7817$afc38c87_at_news.optusnet.com.au>
I am building a website that is based on members, and I am developing an affiliate system for it.
where people can refer others to my site via a link from theirs. This system will also store information on any monetary transactions that are made.
anyway.
my problem is.. where do you draw the line between having a seperate
database for such things?
I am just wondering what the proper database design practice is for
seperating certain features of a site/application into seperate databases.
Or should I just forget about it and stick everything in the one database?
thanks
dan
Received on Sat Jan 04 2003 - 06:30:18 CET