I've tried both and I prefer the central repository. You get all of the benefits of db-driven client vars vs. the registry without having any extra maintenance overhead.
With that said, if you want varying expirations for individual site's vars you'll need to separate them out. I have most systems on a 10-day expiration, but one site wants long-term storage, so I have them on 6 months in their own db. --Matt Robertson-- MSB Designs, Inc. http://mysecretbase.com -----Original Message----- From: Teel, C. Doug [mailto:[EMAIL PROTECTED]] Sent: Friday, February 22, 2002 3:24 PM To: CF-Talk Subject: Client Variable Storage on Mutilple Sites This may be a dumb question, but oh well. I'm setting up a data source[s] to store client variables in cold fusion administrator. We have 3 test sites and a production site running from off a SQL server with each site having it's own database. The question is: Do I need to need to create four different databases to store the client variables for each of these four sites or can I have one server act as a central repository without any possible problems of funky data. Any help greatly appreciated, Doug ______________________________________________________________________ Why Share? Dedicated Win 2000 Server � PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusionc FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
