[EMAIL PROTECTED] [EMAIL PROTECTED] wrote: > > 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.
Some of the limitations of MySQL Cluster are: # The maximum number of metadata objects is limited to 1600, including database tables, system tables, indexes and BLOBs. # The maximum number of attributes per table is limited to 128. # The maximum permitted size of any one row is 8k, not including data stored in BLOB columns. # The maximum number of attributes per key is 32. http://dev.mysql.com/doc/mysql/en/mysql-cluster-limitations-in-4-1.html So I suppose that makes MySQL Cluster less suitable unless you don't mind storing the textarea data in BLOBs. > 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. Isn't it always the same? Pick 2: * affordable * easy * capable :-) Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:203043 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
