You've pretty much covered the pros and cons yourself. It depends what the relative importance of faster queries on current data as aaginst the ease of mutiple year queries. The speed of the queries will depend among other things on the number of records you have and the indexes you have. But unless your're getting above 250k records and your db's not getting too big, say above 200Mb then in my experience I wouldn't have thought querying wouldn't be too hurt much. Why not try it? And if your going to sql then the problem pretty much disappears. Have you thought about MSDE as an interim step? -----Original Message----- From: Andrew Peterson [mailto:[EMAIL PROTECTED]] Sent: 29 March 2001 18:03 To: CF-Talk Subject: OT: Multi year data entry app - database design questions I've got a data entry application which collects data based on fiscal year. What are there any benefits of keeping this multi-year data in the same database vis a vis separating fiscal years into their own databases? I've always chosen to split up the database - otherwise you're doubling db size with little if any interaction with half of it (the old fiscal year), which considerably slows things down when querying I would think. The only reason I see to keep the data within one database is for multi-year research on the data. It seems that quering one database with multiple fiscal years would be easier than doing union queries across multiple databases. For this reason I'm considering keeping it all together in one db. Anyone maintain such a system? Any thoughts greatly appreciated. Currently using MS Access and eventually migrating to SQL Server. Thanks, Andy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
