{"id":1151,"date":"2025-08-08T10:56:34","date_gmt":"2025-08-08T15:56:34","guid":{"rendered":"https:\/\/www.sqltabletalk.com\/?p=1151"},"modified":"2025-08-08T10:56:36","modified_gmt":"2025-08-08T15:56:36","slug":"azure-sql-database-compatibility-levels","status":"publish","type":"post","link":"https:\/\/www.sqltabletalk.com\/?p=1151","title":{"rendered":"Understanding Compatibility Levels in Azure SQL Database"},"content":{"rendered":"


\n<\/p>\n

Introduction<\/h1>\n

When working with Azure SQL Database, you\u2019re operating on a fully managed SQL Server engine that is continually updated behind the scenes. While Microsoft manages the infrastructure, there are still settings and metadata you control that directly affect how your database behaves and how your applications interact with it.<\/p>\n

Three key areas often cause confusion for database administrators and developers:<\/p>\n

    \n
  1. Compatibility levels<\/strong> \u2013 which influence query optimization and certain feature behaviors.<\/li>\n
  2. Database creation dates<\/strong> \u2013 important for audits, migrations, and lifecycle management.<\/li>\n
  3. Engine version reporting<\/strong> \u2013 which tells you the platform build, but not necessarily the feature set your database uses.<\/li>\n<\/ol>\n

    Understanding these concepts is essential for making informed changes, diagnosing performance shifts, and keeping your environment in a healthy, predictable state. This article explains each topic in depth and provides practical T-SQL examples.<\/p>\n

    Compatibility Levels in Azure SQL Database<\/h2>\n

    A compatibility level<\/strong> defines how certain SQL Server features behave and which version of the query optimizer<\/strong> is in use. Think of it as a way to \u201cfreeze\u201d application behavior while still benefiting from Azure\u2019s underlying engine updates.<\/p>\n

    When Microsoft upgrades the Azure SQL Database engine (for example, to align with a newer SQL Server release), your database does not automatically switch<\/strong> to the newer compatibility level. This behavior is intentional \u2014 it avoids breaking applications that may rely on older optimizer rules or T-SQL behaviors.<\/p>\n

    Key facts about compatibility levels:<\/strong><\/p>\n

      \n
    • Compatibility levels are set per database<\/strong>, not server-wide.<\/li>\n
    • They remain fixed<\/strong> until you change them with ALTER DATABASE<\/code>.<\/li>\n
    • They are not tied<\/strong> to the Azure SQL Database engine version \u2014 the two are separate concepts.<\/li>\n<\/ul>\n

      Default compatibility levels over time<\/h3>\n
        \n
      • Before June 2024<\/strong> \u2013 New databases defaulted to level 150<\/strong> (SQL Server 2019 equivalent).<\/li>\n
      • From June 2024 onward<\/strong> \u2013 New databases default to level 160<\/strong> (SQL Server 2022 equivalent).<\/li>\n
      • Level 170<\/strong> \u2013 Planned for SQL Server vNext but not yet generally available as a default in Azure SQL Database at the time of writing.<\/li>\n<\/ul>\n

        Checking your current compatibility level<\/h3>\n

        SELECT name, compatibility_level FROM sys.databases WHERE name = ‘YourDatabaseName’;<\/CODE><\/PRE><\/p>\n
        Changing the compatibility level<\/h3>\n
        ALTER DATABASE [YourDatabaseName] SET COMPATIBILITY_LEVEL = 160;<\/CODE><\/PRE><\/p>\n
        Why compatibility level matters<\/h3>\n
        Changing the compatibility level can impact:<\/p>\n
          \n
        • Query optimizer behavior<\/strong> \u2013 For example, level 160 enables enhancements like Cardinality Estimation (CE) feedback, memory grant feedback, and batch mode on rowstore.<\/li>\n
        • T-SQL syntax and semantics<\/strong> \u2013 Some commands or functions may work differently, or be deprecated, at higher levels.<\/li>\n
        • Performance<\/strong> \u2013 In many cases, newer levels yield better performance. However, if queries depend on older optimizer assumptions, regressions can occur.<\/li>\n<\/ul>\n
          Best practice:<\/em> Test thoroughly in a staging environment before switching. Use Query Store<\/strong> to compare execution plans and runtime metrics before and after the change.<\/p>\n
          Checking When a Database Was Created<\/h2>\n
          Sometimes you need to know exactly when a database was provisioned \u2014 for example, during an audit, when analyzing growth patterns, or when tracing deployment history.<\/p>\n
          In Azure SQL Database, you can retrieve the creation date from the master<\/strong> database (on the same logical server):<\/p>\n
          SELECT name, create_date FROM sys.databases WHERE name = ‘YourDatabaseName’;<\/CODE><\/PRE><\/p>\n
          This date is the original provisioning time of the database \u2014 it does not<\/strong> change if you restore from a backup or copy to another server.<\/p>\n
          Understanding @@VERSION in Azure SQL Database<\/h2>\n
          The @@VERSION<\/code> function is a quick way to see which SQL Server engine build your Azure SQL Database is currently running. In Azure, the output usually looks something like this:<\/p>\n
          \nMicrosoft SQL Azure (RTM) - 12.0.xxxx.x <build info>\n<\/pre>\n
          It\u2019s important to note:<\/p>\n
            \n
          • The \u201c12.0\u201d<\/strong> prefix is fixed for Azure SQL Database and does not change with SQL Server releases \u2014 it\u2019s an internal identifier for Azure\u2019s SQL Database service.<\/li>\n
          • This output reflects the engine build<\/strong>, not your compatibility level<\/strong>.<\/li>\n
          • Microsoft updates the engine automatically as part of the platform; you cannot control this schedule.<\/li>\n<\/ul>\n
            Retrieving the SQL engine version<\/h3>\n
            SELECT @@VERSION;<\/CODE><\/PRE><\/p>\n
            Retrieving the compatibility level<\/h3>\n
            SELECT compatibility_level FROM sys.databases WHERE name = ‘YourDatabaseName’;<\/CODE><\/PRE><\/p>\n
            Putting It All Together<\/h2>\n
            Compatibility levels, creation dates, and engine versions each serve different purposes in Azure SQL Database:<\/p>\n
              \n
            • Compatibility level<\/strong> \u2013 Controls how features behave and how queries are optimized.<\/li>\n
            • Creation date<\/strong> \u2013 Gives you a historical point of reference for the database.<\/li>\n
            • Engine version<\/strong> \u2013 Tells you the current platform build maintained by Microsoft.<\/li>\n<\/ul>\n
              Keeping these distinctions clear helps prevent common misunderstandings \u2014 like assuming the engine version determines available query features, or forgetting to adjust compatibility level after a major application upgrade.<\/p>\n
              Conclusion<\/h2>\n
              Managing Azure SQL Database effectively means understanding the relationship between compatibility levels, creation dates, and engine versions.<\/p>\n
                \n
              • Compatibility levels let you control feature behavior and query optimization without losing stability.<\/li>\n
              • Creation dates provide valuable historical context for database lifecycle tracking.<\/li>\n
              • Engine versions reflect the Azure-managed SQL platform updates but do not dictate your compatibility level.<\/li>\n<\/ul>\n
                By checking these settings regularly and testing changes before applying them in production, you can ensure smoother upgrades, better performance, and fewer surprises in your environment.<\/p>\n","protected":false},"excerpt":{"rendered":"
                When working with Azure SQL Database, you\u2019re operating on a fully managed SQL Server engine that is continually updated behind the scenes. While Microsoft manages the infrastructure, there are still settings and metadata you control that directly affect how your database behaves and how your applications interact with it. We tell you all about it in this blog post.<\/p>\n","protected":false},"author":49,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[101,82],"tags":[626,399,627,159,243,39,90,131,545,344],"class_list":["post-1151","post","type-post","status-publish","format-standard","hentry","category-azure","category-database-configuration","tag-azure-sql-database","tag-cloud-databases","tag-compatibility-level","tag-database-administration","tag-microsoft-azure","tag-performance-tuning","tag-query-optimizer","tag-sql-server","tag-sql-tips","tag-t-sql"],"yoast_head":"\nUnderstanding Compatibility Levels in Azure SQL Database - SQL Table Talk<\/title>\n<meta name=\"description\" content=\"When working with Azure SQL Database, you\u2019re operating on a fully managed SQL Server engine that is continually updated behind the scenes. While Microsoft manages the infrastructure, there are still settings and metadata you control that directly affect how your database behaves and how your applications interact with it. We tell you all about it in this blog post.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.sqltabletalk.com\/?p=1151\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Understanding Compatibility Levels in Azure SQL Database - SQL Table Talk\" \/>\n<meta property=\"og:description\" content=\"When working with Azure SQL Database, you\u2019re operating on a fully managed SQL Server engine that is continually updated behind the scenes. While Microsoft manages the infrastructure, there are still settings and metadata you control that directly affect how your database behaves and how your applications interact with it. We tell you all about it in this blog post.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.sqltabletalk.com\/?p=1151\" \/>\n<meta property=\"og:site_name\" content=\"SQL Table Talk\" \/>\n<meta property=\"article:published_time\" content=\"2025-08-08T15:56:34+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-08-08T15:56:36+00:00\" \/>\n<meta name=\"author\" content=\"Jon Russell\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Jon Russell\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.sqltabletalk.com\/?p=1151#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.sqltabletalk.com\/?p=1151\"},\"author\":{\"name\":\"Jon Russell\",\"@id\":\"https:\/\/www.sqltabletalk.com\/#\/schema\/person\/8f5916388cc3b793a960dea33ff1ed86\"},\"headline\":\"Understanding Compatibility Levels in Azure SQL Database\",\"datePublished\":\"2025-08-08T15:56:34+00:00\",\"dateModified\":\"2025-08-08T15:56:36+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.sqltabletalk.com\/?p=1151\"},\"wordCount\":759,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/www.sqltabletalk.com\/#\/schema\/person\/1947e42a9438bccd91691d8b791888e0\"},\"keywords\":[\"Azure SQL Database\",\"Cloud Databases\",\"Compatibility Level\",\"database administration\",\"Microsoft Azure\",\"performance tuning\",\"Query Optimizer\",\"SQL Server\",\"SQL tips\",\"T-SQL\"],\"articleSection\":[\"Azure\",\"Database Configuration\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.sqltabletalk.com\/?p=1151#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.sqltabletalk.com\/?p=1151\",\"url\":\"https:\/\/www.sqltabletalk.com\/?p=1151\",\"name\":\"Understanding Compatibility Levels in Azure SQL Database - SQL Table Talk\",\"isPartOf\":{\"@id\":\"https:\/\/www.sqltabletalk.com\/#website\"},\"datePublished\":\"2025-08-08T15:56:34+00:00\",\"dateModified\":\"2025-08-08T15:56:36+00:00\",\"description\":\"When working with Azure SQL Database, you\u2019re operating on a fully managed SQL Server engine that is continually updated behind the scenes. While Microsoft manages the infrastructure, there are still settings and metadata you control that directly affect how your database behaves and how your applications interact with it. We tell you all about it in this blog post.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.sqltabletalk.com\/?p=1151#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.sqltabletalk.com\/?p=1151\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.sqltabletalk.com\/?p=1151#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.sqltabletalk.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Understanding Compatibility Levels in Azure SQL Database\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.sqltabletalk.com\/#website\",\"url\":\"https:\/\/www.sqltabletalk.com\/\",\"name\":\"SQL Table Talk\",\"description\":\"Breaking Down SQL Server, One Post at a Time.\",\"publisher\":{\"@id\":\"https:\/\/www.sqltabletalk.com\/#\/schema\/person\/1947e42a9438bccd91691d8b791888e0\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.sqltabletalk.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/www.sqltabletalk.com\/#\/schema\/person\/1947e42a9438bccd91691d8b791888e0\",\"name\":\"Stephen Planck\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.sqltabletalk.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/64181114edc3de3d99072c049bcec024f025c9536dc89fc8ff1bac58976ca81e?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/64181114edc3de3d99072c049bcec024f025c9536dc89fc8ff1bac58976ca81e?s=96&d=mm&r=g\",\"caption\":\"Stephen Planck\"},\"logo\":{\"@id\":\"https:\/\/www.sqltabletalk.com\/#\/schema\/person\/image\/\"},\"sameAs\":[\"https:\/\/dexterwiki.com\",\"https:\/\/www.linkedin.com\/in\/stephen-planck-4611b692?trk=people-guest_people_search-card&challengeId=AQErf8gbBmcVMwAAAYsyIsxO-0UvU8z7cHrBpZoo_n3xt9qEKpRN5B_jd_LmAMu-OfeArkQ7GDjobJ2uRoQQV35EQdh_rR6kxA&submissionId=09de7067-c335-8e17-40b8-8dc32b60ed6c&challengeSource=AgEcUCw35zpPmAAAAYsyI4vAWhJTV7Nt4vZYKc3V1qiDBpCkKgUvtlOBgYXcE84&challegeType=AgE_wZiTT09IAQAAAYsyI4vDmNvbZIYe6XHju5V2bXVvM3IVxnJslgY&memberId=AgESFTkUShzs_gAAAYsyI4vGYk0Gic1uc5kB6cKOABA26Gw&recognizeDevice=AgHdSZyUSI5CEwAAAYsyI4vKd_koF9JgpsCJShT8QfbK1QMiv8SI\",\"https:\/\/www.youtube.com\/linuxmate\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.sqltabletalk.com\/#\/schema\/person\/8f5916388cc3b793a960dea33ff1ed86\",\"name\":\"Jon Russell\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.sqltabletalk.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f35049bc3903cae9c596247b2dfe95c0d9b003dd0c758b9690cc00544216aa7c?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/f35049bc3903cae9c596247b2dfe95c0d9b003dd0c758b9690cc00544216aa7c?s=96&d=mm&r=g\",\"caption\":\"Jon Russell\"},\"url\":\"https:\/\/www.sqltabletalk.com\/?author=49\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Understanding Compatibility Levels in Azure SQL Database - SQL Table Talk","description":"When working with Azure SQL Database, you\u2019re operating on a fully managed SQL Server engine that is continually updated behind the scenes. While Microsoft manages the infrastructure, there are still settings and metadata you control that directly affect how your database behaves and how your applications interact with it. We tell you all about it in this blog post.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.sqltabletalk.com\/?p=1151","og_locale":"en_US","og_type":"article","og_title":"Understanding Compatibility Levels in Azure SQL Database - SQL Table Talk","og_description":"When working with Azure SQL Database, you\u2019re operating on a fully managed SQL Server engine that is continually updated behind the scenes. While Microsoft manages the infrastructure, there are still settings and metadata you control that directly affect how your database behaves and how your applications interact with it. We tell you all about it in this blog post.","og_url":"https:\/\/www.sqltabletalk.com\/?p=1151","og_site_name":"SQL Table Talk","article_published_time":"2025-08-08T15:56:34+00:00","article_modified_time":"2025-08-08T15:56:36+00:00","author":"Jon Russell","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Jon Russell","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.sqltabletalk.com\/?p=1151#article","isPartOf":{"@id":"https:\/\/www.sqltabletalk.com\/?p=1151"},"author":{"name":"Jon Russell","@id":"https:\/\/www.sqltabletalk.com\/#\/schema\/person\/8f5916388cc3b793a960dea33ff1ed86"},"headline":"Understanding Compatibility Levels in Azure SQL Database","datePublished":"2025-08-08T15:56:34+00:00","dateModified":"2025-08-08T15:56:36+00:00","mainEntityOfPage":{"@id":"https:\/\/www.sqltabletalk.com\/?p=1151"},"wordCount":759,"commentCount":0,"publisher":{"@id":"https:\/\/www.sqltabletalk.com\/#\/schema\/person\/1947e42a9438bccd91691d8b791888e0"},"keywords":["Azure SQL Database","Cloud Databases","Compatibility Level","database administration","Microsoft Azure","performance tuning","Query Optimizer","SQL Server","SQL tips","T-SQL"],"articleSection":["Azure","Database Configuration"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.sqltabletalk.com\/?p=1151#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.sqltabletalk.com\/?p=1151","url":"https:\/\/www.sqltabletalk.com\/?p=1151","name":"Understanding Compatibility Levels in Azure SQL Database - SQL Table Talk","isPartOf":{"@id":"https:\/\/www.sqltabletalk.com\/#website"},"datePublished":"2025-08-08T15:56:34+00:00","dateModified":"2025-08-08T15:56:36+00:00","description":"When working with Azure SQL Database, you\u2019re operating on a fully managed SQL Server engine that is continually updated behind the scenes. While Microsoft manages the infrastructure, there are still settings and metadata you control that directly affect how your database behaves and how your applications interact with it. We tell you all about it in this blog post.","breadcrumb":{"@id":"https:\/\/www.sqltabletalk.com\/?p=1151#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.sqltabletalk.com\/?p=1151"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.sqltabletalk.com\/?p=1151#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.sqltabletalk.com\/"},{"@type":"ListItem","position":2,"name":"Understanding Compatibility Levels in Azure SQL Database"}]},{"@type":"WebSite","@id":"https:\/\/www.sqltabletalk.com\/#website","url":"https:\/\/www.sqltabletalk.com\/","name":"SQL Table Talk","description":"Breaking Down SQL Server, One Post at a Time.","publisher":{"@id":"https:\/\/www.sqltabletalk.com\/#\/schema\/person\/1947e42a9438bccd91691d8b791888e0"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.sqltabletalk.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/www.sqltabletalk.com\/#\/schema\/person\/1947e42a9438bccd91691d8b791888e0","name":"Stephen Planck","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.sqltabletalk.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/64181114edc3de3d99072c049bcec024f025c9536dc89fc8ff1bac58976ca81e?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/64181114edc3de3d99072c049bcec024f025c9536dc89fc8ff1bac58976ca81e?s=96&d=mm&r=g","caption":"Stephen Planck"},"logo":{"@id":"https:\/\/www.sqltabletalk.com\/#\/schema\/person\/image\/"},"sameAs":["https:\/\/dexterwiki.com","https:\/\/www.linkedin.com\/in\/stephen-planck-4611b692?trk=people-guest_people_search-card&challengeId=AQErf8gbBmcVMwAAAYsyIsxO-0UvU8z7cHrBpZoo_n3xt9qEKpRN5B_jd_LmAMu-OfeArkQ7GDjobJ2uRoQQV35EQdh_rR6kxA&submissionId=09de7067-c335-8e17-40b8-8dc32b60ed6c&challengeSource=AgEcUCw35zpPmAAAAYsyI4vAWhJTV7Nt4vZYKc3V1qiDBpCkKgUvtlOBgYXcE84&challegeType=AgE_wZiTT09IAQAAAYsyI4vDmNvbZIYe6XHju5V2bXVvM3IVxnJslgY&memberId=AgESFTkUShzs_gAAAYsyI4vGYk0Gic1uc5kB6cKOABA26Gw&recognizeDevice=AgHdSZyUSI5CEwAAAYsyI4vKd_koF9JgpsCJShT8QfbK1QMiv8SI","https:\/\/www.youtube.com\/linuxmate"]},{"@type":"Person","@id":"https:\/\/www.sqltabletalk.com\/#\/schema\/person\/8f5916388cc3b793a960dea33ff1ed86","name":"Jon Russell","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.sqltabletalk.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/f35049bc3903cae9c596247b2dfe95c0d9b003dd0c758b9690cc00544216aa7c?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f35049bc3903cae9c596247b2dfe95c0d9b003dd0c758b9690cc00544216aa7c?s=96&d=mm&r=g","caption":"Jon Russell"},"url":"https:\/\/www.sqltabletalk.com\/?author=49"}]}},"jetpack_featured_media_url":"","jetpack-related-posts":[],"jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/www.sqltabletalk.com\/index.php?rest_route=\/wp\/v2\/posts\/1151","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sqltabletalk.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sqltabletalk.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sqltabletalk.com\/index.php?rest_route=\/wp\/v2\/users\/49"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sqltabletalk.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1151"}],"version-history":[{"count":12,"href":"https:\/\/www.sqltabletalk.com\/index.php?rest_route=\/wp\/v2\/posts\/1151\/revisions"}],"predecessor-version":[{"id":1177,"href":"https:\/\/www.sqltabletalk.com\/index.php?rest_route=\/wp\/v2\/posts\/1151\/revisions\/1177"}],"wp:attachment":[{"href":"https:\/\/www.sqltabletalk.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1151"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sqltabletalk.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1151"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sqltabletalk.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1151"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}