Djabarov, Robert
Robert.Djabarov at usaa.com
Mon Dec 15 15:25:25 CST 2003
1. 8000-character fields do not impact your performance any more than 255-character fields do. 2. Nope, keep it together with the rest of the fields, unless those 20% may have total length entered greater or equal to the row length limitations, in which case your INSERT/UPDATE will fail. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Susan Geller Sent: Monday, December 15, 2003 2:53 PM To: dba-SQLServer at databaseadvisors.com Subject: [dba-SQLServer]Large varchar fields -- performance implications? I am working on a data model and have some questions about large (that is over 255) sized varchar fields. 1. Does it matter what size the varchar is once it is over 255? That is, do you take the same performance hit for a varchar 260 as for a varchar 8000? 2. If I have a field in a table that needs to be over varchar(255), but will only be populated about 20% of the time, should I put that field in its own table with an id value and just store the id value in the table? In other words, do I take a performance hit even when my field is empty? --Susan Susan B. Geller Office of Information Systems College of Continuing Education University of Minnesota 306 Wesbrook Hall 77 Pleasant Street SE Minneapolis, MN 55455 Phone: 612-626-4785 Fax: 612-625-2568 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com