On Fri, Jan 3, 2014 at 12:44 PM, Paul McNett <[email protected]> wrote:
> On 1/3/14 10:00 AM, Ed Leafe wrote: > > On Jan 3, 2014, at 10:28 AM, MB Software Solutions General Account < > [email protected]> wrote: > > > >> I just feel dirty setting everything to varchar(255). lol > > > > Worth a read: > http://eflorenzano.com/blog/2008/11/11/why-use-varchar-when-you-can-use-text/ > > ( -or- http://j.mp/1l7rhew ) > > I had a DBA switch my schema from using TEXT to VARCHAR(max) which I guess > is a > feature of MS-SQL. I just trusted that he knew better but it still rankles. > ---------------- Let the engine decide via varchar(max) By using VARCHAR(MAX) you are basically telling SQL Server "store the values in this field how you see best", SQL Server will then choose whether to store values as a regular VARCHAR or as a LOB (Large object). *In general if the values stored are less than 8,000 bytes SQL Server will treat values as a regular VARCHAR type.* -- Stephen Russell Sr. Analyst Ring Container Technology Oakland TN 901.246-0159 cell --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cajidmyl4xsa7jiw9wt3fa9x75puoqnawtq8whmnigczdrau...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
