The article actually suggests to me that using larger than 64K might be beneficial to Spectra. Since acess to an object with extendeddata always acesses the extended part and the base part, it seems like a single hit to the database for all the data would be more efficient.
My impressions of why the 64K limit are: - Maximize compatibility across database engines (some have limits) - Maximize compatibility across versions of CF as earlier versions had limits on DB record size - Eliminate false bug reports on CF versions that support >64K but which are not configured to allow that size. Rich ----- Original Message ----- From: "Aaron Johnson" <[EMAIL PROTECTED]> To: "Spectra-Talk" <[EMAIL PROTECTED]> Sent: Tuesday, November 27, 2001 7:47 AM Subject: RE: Object Size > Hey Shawn, > > > Thanks for the info. I still don't understand the splitting, as > > the db uses > > a text field which can hold up to 2 gigs, since it's just a pointer to a > > location on the disk anyway (SQLServer). > == It has nothing to do with the size of the field in SQL Server.. it's > getting from Spectra to SQLServer via your DB driver... the size of the > packet that travels from your webserver to the DB server is limited by the > driver, more information on the limitations here: > > http://www.sdmagazine.com/documents/s=791/sdm9611a/9611a.htm (do a quick > search through the article for packet sizes) > > Aaron Johnson, MCSE, MCP+I > Macromedia Certified ColdFusion Developer > MINDSEYE, Inc. > <phn>617.350.0339 > <mbl>617.461.3721 > <fax>617.350.8884 > <icq>66172567 > [EMAIL PROTECTED] > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com ------------------------------------------------------------------------------ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
