That's interesting, I seem to remember a thread on the list a while ago about the best practices for maintenance and security saying that each DB should be fairly narrowly focused.
Some of the data is not necessarily related to each other, but more related in that I'd like to be able to do a zip-code statistical look at things in a couple different tables. For instance, I have an Information and Referral database where I need to do zip code lookups. I also have a users database that I would like to do a zip code lookup. Also many of these separate DBs are specific to an application. Oddly enough as I write this i'm seeing way that these things *should* be in the same database. So I guess this turns my question into one of "how do I take many different apps developed over many years and integrate them together..." :-) Let me narrow the focus a bit. Specifically I have a zipcode database that I need to use in various DBs. Is there a "best way" to keep this data current across all instances? Should I replicate it when I install the new one? Thanks, John -----Original Message----- From: Jeffry Houser [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 05, 2003 3:12 PM To: CF-Talk Subject: Re: DB Strategy You can use ColdFusion's query of a query feature to do this. A more complex route is to write your own custom code to put two queries together into a new query using the query functions. However, I do question the comment that you shouldn't put everything in a big database. Yes, I agree that sometimes there are reasons; such as the data being in no way related. ( For instance, the web site dedicated to my books vs the web site dedicated to my band ). If you are talking about related data, I might make the argument that there is no reason to store it in different databases. Different tables, yes. Different databases, probably not. Of course, it depends on your data and usage. I'm curious (Perhaps even obsessing) over why the data is in different DBs if it needs to be related. At 02:09 PM 2/5/2003 -0500, you wrote: >Over time I have created many little web apps that parts of our organization >use. Inevitably there's time when I also want to utilize that data in the DB >to pull it to the website, often times relating it to another table that may >be in another DB. I know there are a variety of different reasons not to put >everything in one big database, but how does one relate disparate >Datasources? What are the various strategies for this, I can think of some >(i.e. DTS duplicating tables) but I wanna know what the big guys are doing. > >(one quick example of what I am meaning is a zip code DB which I want to be >able to relate to a bunch of other tables in various other DBs.) > >Thanks much, > >John > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
