Hi. I wondered what the current line of thinking on this is, I have several databases with the exact same information in them. Say we have a "members" set of information. This information has their name, address, business address, every possible phone number, driver's license number and on and on. Currently the information is repeated in 5 or 6 different databases. (databases not tables within a db)
I was wondering if it would be smarter to have that all in one database and then break the specifics down in smaller dbs. For example. Member info in one database with an ID that designates them uniquely. Now, say that member has a license to sell books in Florida but not Texas. So the Florida database would connect to that person via the unique ID. Then on another db note that the florida member gets a 10% commission on sold books, while the member in Texas gets a 7% commission. Then on another db connected again by the unique ID, the 7% commision earning member is part of the Gold club because he has sold over a million books. The Florida member is part of the silver club because this member has only sold a half a million accounts - and so on and so forth.
Currently the same infos are put in each db. The member info is in a database for commissions. Then it is in another completely different db with the license information. Then another completely different database with the type of books that can be sold. etc, etc.
I can see pros and cons for both. But I am at a total redesign on a legacy because we have grown so much that a single query and submit is taking 13-15 minutes. - really not time efficient now is that? -
So do you know the current thought?