Madeira Data Solutions
  • Home

  • About Us

    • Our Team
    • Customers
    • Join Us
  • Managed Services

  • Professional Services

  • Training Services

  • Content Hub

    • Blog
    • Webinars
    • Podcast- SQL SERVER RADIO
  • More

    Use tab to navigate through the menu items.

    Contact Us

    • All Posts
    • SQL Server
    • Podcasts
    • PASS
    • SQL Server 2012
    • Big Data
    • Cloud
    • Scripts
    • Blog
    • DMV's
    • Learning
    • Performance
    • SQL Server 2012
    • Conferences
    • Cursors
    • Plan Cache
    • SQL Agent
    • SQL Azure
    • High Availability
    • Productivity
    • Downloads
    • SQL Server 2014
    • SQL Server 2016
    • Webcasts
    • Videos
    • Troubleshooting
    • SQL Server 2017
    • Tools
    • SQLServerPedia Syndication
    • Storage
    • TempDB
    Search
    Madeira Team
    • Jul 27, 2012
    • 1 min

    max data types performance

    On some occasions, migrating from text, ntext or image to varchar(max), nvarchar(max) or varbinary(max) can hurt performance. How is that possible? Well, when using text, ntext and image, SQL Server’s default behavior is to keep the LOB data outside of the row, and it just adds each row a 16 byte pointer that references to the place where the relevant LOB information is stored. When using max fields, the default is the opposite. Up to a size of 8000 bytes, SQL Server keeps LO

    0

    keep in Touch!

    JOIN OUR MAILING LIST

    CONTACT US

    4 Itzhak Ben Zvi, Hod-Ha'sharon, Israel 4537302

     +972-9-7400101

    info@madeiradata.com

    About Us
    Solutions
    Data Architecture Review
    DBSMART
    Database Health Check
    SQL Server Upgrade
    Join Us

    Privacy Policy

    • Google+ - White Circle
    • Facebook - White Circle
    • Twitter - White Circle
    • LinkedIn - White Circle