Re: When does using multiple databases make sense?
Sorry Robert, didn't mean to send to only you. We're developing a management program that can manage several jobs that a construction company is working on. We have a separate database for each job that is installed in the program. This eliminates the need to keep an extra field in each table that designates which job the record is for. We simply have a connection open to the appropriate database that the user is working with. There are times that I wonder if this was an appropriate design, but for the most part, I think its the most simplistic way of coding it. Matt At 11:47 AM 1/8/2004, you wrote: In our accounting software our users can manage the books for several different companies with the same program. As such I have to keep a field (in every record) that designates which company the given record is for and use it for report filtering, lookups, etc. Had I used a different database for each company then I would not need the overhead of this field. We chose the company field over the multiple databases because many of our clients are vertically integrated and do cross charging (an entry from one company posts to another company). This inter-company stuff is easy if the data is all in one database but we always have to remember to filter by the company field everywhere else. If I had it to do over again I'd probably use multiple databases. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: When does using multiple databases make sense?
I would still keep them in one database. My experience is that duplication of code (in this case tables) leads to maintaince headaches. Plus this way, you can backup/restore easily, and if necessary, once 5.0 comes out, you can use views per client to limit selects, I suppose... My $0.02 Dan Greene > -Original Message- > From: robert_rowe [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 08, 2004 12:48 PM > To: [EMAIL PROTECTED] > Subject: Re: When does using multiple databases make sense? > > > > In our accounting software our users can manage the books for > several different companies with the same program. As such I > have to keep a field (in every record) that designates which > company the given record is for and use it for report > filtering, lookups, etc. Had I used a different database for > each company then I would not need the overhead of this > field. We chose the company field over the multiple databases > because many of our clients are vertically integrated and do > cross charging (an entry from one company posts to another > company). This inter-company stuff is easy if the data is all > in one database but we always have to remember to filter by > the company field everywhere else. If I had it to do over > again I'd probably use multiple databases. > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: When does using multiple databases make sense?
In our accounting software our users can manage the books for several different companies with the same program. As such I have to keep a field (in every record) that designates which company the given record is for and use it for report filtering, lookups, etc. Had I used a different database for each company then I would not need the overhead of this field. We chose the company field over the multiple databases because many of our clients are vertically integrated and do cross charging (an entry from one company posts to another company). This inter-company stuff is easy if the data is all in one database but we always have to remember to filter by the company field everywhere else. If I had it to do over again I'd probably use multiple databases. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: When does using multiple databases make sense?
On 8 Jan 2004, at 04:12, Paul F wrote: Greetings, I am wandering under what circumstances it is sensible/beneficial to use multiple databases for a single "project," and why. The reason I ask is because I am re-developing an existing database with MySQL that someone else created with another engine (DBISAM) and chose to have 5 separate databases used by one application. I've worked on a project where we had 2 databases; one was for "live" data, the other was used when the application switched to a training mode and so couldn't affect live data. It was a Windows app and connection was via ODBC. We had 2 ODBC sources set up to point to same server, but a different database. (Actually, it was a MS SQL Server, but the same principles apply). It was a simple matter of deciding which source to use depending on whether the app was in training mode or not. I can't think of a reason for 5! :) Steve. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
When does using multiple databases make sense?
Greetings, I am wandering under what circumstances it is sensible/beneficial to use multiple databases for a single "project," and why. The reason I ask is because I am re-developing an existing database with MySQL that someone else created with another engine (DBISAM) and chose to have 5 separate databases used by one application. And yes, I do mean databases not tables LOL. Thanks for any advice! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
