Keith, You and your users will probably make a judgement call on the database issues you have raised. There are pros and cons to everything. And after you go one direction with regard to database design for awhile, you may change your mind and go the opposite. [The pendulum swings both ways!]
For example: At the enterprize level, after many years of normalizing their relational databases, many companies are finding that datamart and data warehouses, providing instantaneous results from tables that have millions of records (rows), are possible only with de-normalized databases. To everything there is an advantage (and disadvantage). Eric Lehti 913-638-1049 -----Original Message----- From: Keith Purtell [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 21, 2002 1:47 PM To: KCFusion (E-mail) Subject: [KCFusion] Consolidating databases I'm converting our databases from Access to MS SQL7. The Upsizing Wizard has handled everything. My question is about consolidating databases. For example I built a CF interface that lets managers upload files and add page content. File locations and descriptions, and text for page content, is stored in Access databases. Each database has about four tables. It occurs to me I could simplify by having all Web-based administration in one SQL database. What I don't know is whether it would be best in the long run to consolidate by function, or perhaps by department. I suppose it's possible that some day Marketing would insist that it's data be separate from Accounting. Comments? Keith Purtell, Web/Network Administrator VantageMed Operations (Kansas City) Email: [EMAIL PROTECTED] ______________________________________________________________________ The KCFusion.org list and website is hosted by Humankind Systems, Inc. List Archives........ http://www.mail-archive.com/[email protected] Questions, Comments or Glowing Praise.. mailto:[EMAIL PROTECTED] To Subscribe.................... mailto:[EMAIL PROTECTED] To Unsubscribe................ mailto:[EMAIL PROTECTED]
