Seems to me that as long as all the contacts / reachability info / URIs are distinct for each user, there is not a problem with using one big database, and that it certainly presents less of a maintenance headache. It also provides easier migration path to future options you may want to explore that *do* take advantage of its shared aspect.
On Wed, 22 Aug 2007, Peder @ NetworkOblivion wrote: > I am in the process of setting up several * servers using realtime and > connecting to mysql. I am trying to figure out if I should just use one > database and one set of tables for all of the user data. Or if I should > have separate databases for each * box. The boxes are independent of > each other in that customerA only connects to box A. They will never > fail over to box B or anything like that. I want to use realtime for > queues,voicemail, sippeers and extensions. The only issue that I have > come up with so far is that a common voicemail table would cause each > box to try and send out mwi indicators since it appears each * box pulls > all of the voicemail boxes from the DB every 10 seconds. > > Any thoughts on whether I should go with one DB, or separate per box > DB's? There is one mysql box, I am not referring to mysql on each box, > I am referring to whether I should use separate DB's within the one > mysql box for each * box. Thanks. > > Peder > > > _______________________________________________ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > -- Alex Balashov Evariste Systems Web : http://www.evaristesys.com/ Tel : +1-678-954-0670 Direct : +1-678-954-0671 _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
