Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.ms-sqlserver    |    Notorious Rube Goldberg contraption    |    19,505 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 19,192 of 19,505    |
|    Erland Sommarskog to rja.carnegie@gmail.com    |
|    Re: Best Practices for Wide Columns in T    |
|    07 May 15 21:29:32    |
      From: esquel@sommarskog.se               (rja.carnegie@gmail.com) writes:       > As of SQL Server 2005 (about to be retired, and maybe       > me with it), you can declare varchar(max) which -       > typically? - is stored in a separate page (LOB_DATA) but       > usually can be treated just like varchar(9) in your SQL       > statements - likewise nvarchar, varbinary - or formats       > like varchar(999) which are stored either IN_ROW_DATA       > if it'll fit, or ROW_OVERFLOW_DATA if not.              By default, the MAX data types are stored on the data page, as long       as they are < 8000 bytes. There is a table option to change this.              > I think there /used/ to be an option to hold short       > values of an unlimited-length column as IN_ROW_DATA -       > maybe that was for [text] and [ntext] types?              For text/ntext/image, the default is to store out of row, but there is       an option to change this as well.                                   --       Erland Sommarskog, Stockholm, esquel@sommarskog.se              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca