By mswatcher
via sqlblog.com
Submitted: Jan 31 2013 / 12:12
Enabling compression on your database can save you a lot of space – but when you have a lot of varchar(max) or nvarchar(max) data, you may find the savings to be limited. This is because only data stored on the data and index pages is compressed, and data for the (max) data types is generally stored on other, special-purpose pages – either text/image pages, or row overflow data pages. (See Understanding Pages and Extents in Books Online). This is from the SQL Server 2008R2 Books Online, but it is still valid in SQL Server 2012 – but apparently, this page has been removed from newer Books Online editions).
-
A look at some of Python's useful itertools
-
Use Web Components Today With Google's Polymer
-
How to reduce the app rejection on iTunes Store
-
Good/Bad Code Study: Intention Hidden In Implementation And Misty Edge of Validity
-
Programmer Interrupted
-
Vert.x + Yoke (Polyglot Answer to Node.js + Express) + WebSockets on many clouds
Add your comment
