> With this hardware config, what is the best way to have CF > configured for client variable storage? One of my main > concerns was if the SQL box dropped for any reason, it > would lock up CF.
That should be a pretty minor concern, for two reasons: 1. If the SQL Server drops, your apps won't be able to do very much anyway. 2. Your SQL Server should generally be much more stable than your web/application server. > If registry storage is the best performance choice, what is > the best method of purging the reg entries? Storing Client variables in the Registry may be the best performer in the short term, but not over the longer haul - the Registry gets slower over time (it's not designed to be a transactional database) and it fragments, just like a filesystem. In addition, it's prone to corruption and failure. > Lastly, What's better for the DB connection? Named Pipes or > TCP/IP with this setup? I've had no serious problems with either, but typically use TCP/IP directly, because it's usually simpler to administer (for example, you don't need to have Windows Networking - NetBIOS/SMB/DirectHost/etc capability between the two machines). Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. ------------------------------------------------------------------------------ To unsubscribe, send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body or visit the list page at www.houseoffusion.com
