...but obviously from an admin perspective it makes sense to break up the data, into managable chunks, eg. one db per site/project etc..
WG -----Original Message----- From: Scott Weikert [mailto:[EMAIL PROTECTED] Sent: 07 July 2003 18:37 To: CF-Talk Subject: Re: How many tables a datasource can handle? At 02:31 PM 7/7/2003 -0300, you wrote: >I'm wondering when it's time to split a datasource that has many tables into >two or more. I never saw an article or recommendation on this. > >Anyone knows if the number of tables can decrease performance? I asked this some weeks back. The answer I got was, a database (SQL7 at least) can have around 2.1 million 'objects' (not sure if this was the term used) - those being tables, views, stored procedures, etc etc etc. So unless you've got several hundred thousand tables, I don't think you're in any danger. :) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
