> [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: > > > > The ideal solution would be transparent to the application and > wouldn't put any undue restrictions on schema. > > Which datatypes do you intend to use? CLOB / text or just small > varchar fields and integers? Stored procedures / DB side > programming? Any need for fulltext indexes?
[The following refers to MSSQL datatypes, etc., but keep in mind I'm still db-neutral.] Since the architecture would probably only service our large surveys, I can be pretty sure that it will be 99% tinyint, int, bit, and varchar(256), and maybe 1% textarea (varchar(4000)). However, sometimes, we have several textareas, and I get uncomfortable about the MSSQL 8k row limit, so I'll probably move textareas to "text" datatypes soon. Also, the response table is generally very flat, with a column per data point (meaning many columns). There are currently no sprocs, views, cursor, full text indexes, etc., servicing the surveys, it's all straight (simple) SQL at the moment. When I first posed the question, I was hoping to get a solution that would service any of our apps, not just our surveys, but if we need/ought to specialize it for our surveys (which have the clustering requirements), then that's fine. Thanks again for the questions and resplies, Jamie ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:203037 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
