You would like need to use a CLOB field instead of a varchar in this case. There is no limit to the amount of data you can store in a CLOB field. Depending on what database you are using, the field data type may be called something else e.g. text with SQL Server. Further, Oracle supports a field data type of BFile, which is a pointer to actual file system file.
Matt Liotta President & CEO Montara Software, Inc. http://www.montarasoftware.com/ V: 415-577-8070 F: 415-341-8906 P: [EMAIL PROTECTED] > -----Original Message----- > From: Joshua Miller [mailto:[EMAIL PROTECTED]] > Sent: Thursday, August 15, 2002 8:24 PM > To: CF-Talk > Subject: XML vs. SQL with large amounts of text > > Ok, this may be a stupid question, but when choosing a data storage > method (XML vs. SQL) what is the best method to store large amounts of > text? > > I've got a scenario where I will have 30,000+ Businesses in a database > and each Business will have at least one report of considerable length. > I'm currently storing every report as an XML document with a naming > convention that is the same as the business ID. I considered using SQL > to store each report as a glob of XML, but the XML documents may exceed > the 8000 character limit of a SQL field. Is there something larger than > that field or is it more advisable to use XML documents for each report? > > Each XML Document at their smallest will be appx 6-8k, at their largest > will be < 30k. Is it advisable to stuff the XML contents into a SQL > table instead as storing as XML files? > > Any insight appreciated. > > Thanks, > > Joshua Miller > > ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm 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
