{"id":1032,"date":"2019-08-08T06:00:31","date_gmt":"2019-08-08T13:00:31","guid":{"rendered":"http:\/\/3.209.169.194\/blogs\/erin\/?p=1032"},"modified":"2019-08-08T06:26:07","modified_gmt":"2019-08-08T13:26:07","slug":"what-columns-are-in-that-index","status":"publish","type":"post","link":"https:\/\/www.sqlskills.com\/blogs\/erin\/what-columns-are-in-that-index\/","title":{"rendered":"What columns are in that index?"},"content":{"rendered":"

I\u2019ve been helping several customers with tuning lately, which typically means I\u2019m also looking at indexes and asking questions. A pattern I\u2019ve noticed is columns from the clustering key being added to the key definition for the nonclustered index.\u00a0 This brings up some interesting considerations when it comes to creating your nonclustered indexes.<\/p>\n

Review<\/h1>\n

We\u2019re going to start with a copy of WideWorldImporters, and create a table and indexes from it.
\nNotice that I\u2019m adding a column to this table named OrderID_and_OrderLineID, which is the OrderID and the OrderLineID values concatenated. In Sales.OrderLines, OrderLine is unique, but OrderID is not. The two of them concatenated are unique, and I made this my primary key, as well as my clustering key (remember, you can have a primary key that\u2019s different than your clustering key, which is a separate topic for another day).<\/p>\n

\r\nUSE [WideWorldImporters]\r\nGO\r\n\r\nDROP TABLE IF EXISTS [Sales].[SQLskills_OrderLines];\r\nGO\r\n\r\nCREATE TABLE [Sales].[SQLskills_OrderLines](\r\n     [OrderLineID] [int] NOT NULL,\r\n     [OrderID] [int] NOT NULL,\r\n     [OrderID_and_OrderLineID] [bigint] NOT NULL,\r\n     [StockItemID] [int] NOT NULL,\r\n     [Description] [nvarchar](100) NOT NULL,\r\n     [PackageTypeID] [int] NOT NULL,\r\n     [Quantity] [int] NOT NULL,\r\n     [UnitPrice] [decimal](18, 2) NULL,\r\n     [TaxRate] [decimal](18, 3) NOT NULL,\r\n     [PickedQuantity] [int] NOT NULL,\r\n     [PickingCompletedWhen] [datetime2](7) NULL,\r\n     [LastEditedBy] [int] NOT NULL,\r\n     [LastEditedWhen] [datetime2](7) NOT NULL,\r\n     CONSTRAINT [PK_Sales_SQLskills_OrderLines] PRIMARY KEY CLUSTERED\r\n     (\r\n          [OrderID_and_OrderLineID] ASC\r\n     )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, \r\n     ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [USERDATA]\r\n     ) ON [USERDATA];\r\nGO\r\n\r\nINSERT INTO [Sales].[SQLskills_OrderLines](\r\n     [OrderLineID]\r\n     ,[OrderID]\r\n     ,[OrderID_and_OrderLineID]\r\n     ,[StockItemID]\r\n     ,[Description]\r\n     ,[PackageTypeID]\r\n     ,[Quantity]\r\n     ,[UnitPrice]\r\n     ,[TaxRate]\r\n     ,[PickedQuantity]\r\n     ,[PickingCompletedWhen]\r\n     ,[LastEditedBy]\r\n     ,[LastEditedWhen]\r\n     )\r\nSELECT\r\n     [OrderLineID]\r\n     ,[OrderID]\r\n     ,CAST(CAST([OrderID] AS VARCHAR(20)) + CAST([OrderLineID] AS VARCHAR(20)) AS BIGINT)\r\n     ,[StockItemID]\r\n     ,[Description]\r\n     ,[PackageTypeID]\r\n     ,[Quantity]\r\n     ,[UnitPrice]\r\n     ,[TaxRate]\r\n     ,[PickedQuantity]\r\n     ,[PickingCompletedWhen]\r\n     ,[LastEditedBy]\r\n     ,[LastEditedWhen]\r\nFROM [Sales].[OrderLines];\r\nGO\r\n<\/pre>\n
We\u2019ll use Kimberly\u2019s version<\/a> of sp_helpindex, sp_SQLskills_helpindex, to see what\u2019s truly in<\/em> the index, and where. I much prefer this version to the built-in sp_helpindex, as it includes information about included columns, filters, and tells you what columns are in the tree and leaf levels.<\/p>\n
\r\nEXEC sp_SQLskills_helpindex 'Sales.SQLskills_OrderLines';\r\nGO\r\n<\/pre>\n
\"Clustered
Clustered index for SQLskills_OrderLines<\/figcaption><\/figure>\n
This output is wide, which doesn\u2019t lend itself well to a post, so you may need to zoom in on the image. I also trimmed out the included and filtered columns as neither are relevant in this discussion.<\/p>\n
Notice that the only column in columns_in_tree is the concatenated OrderID and OrderLineID, and then all columns are in columns_in_leaf (because the leaf level of the clustered index is all the data).\u00a0 Now we\u2019ll add a nonclustered index on OrderID:<\/p>\n
\r\nCREATE NONCLUSTERED INDEX [NCI_OrderID]\r\n     ON [Sales].[SQLskills_OrderLines] ([OrderID])\r\n     ON [USERDATA];\r\nGO\r\n\r\nEXEC sp_SQLskills_helpindex 'Sales.SQLskills_OrderLines';\r\nGO\r\n<\/pre>\n
\"Nonclustered
Nonclustered index for SQLskills_OrderLines<\/figcaption><\/figure>\n
In columns_in_tree we have our index key, OrderID, but we also have our clustering key, OrderID_and_OrderLineID, and both are in columns_in_leaf. What happens if we create a nonclustered index on OrderLineID, and make it unique?<\/p>\n
\r\nCREATE UNIQUE NONCLUSTERED INDEX [NCI_OrderLineID]\r\n     ON [Sales].[SQLskills_OrderLines] ([OrderLineID])\r\n     ON [USERDATA];\r\nGO\r\n\r\nEXEC sp_SQLskills_helpindex 'Sales.SQLskills_OrderLines';\r\nGO\r\n<\/pre>\n
\"Unique
Unique nonclustered index for SQLskills_OrderLines<\/figcaption><\/figure>\n
In the sp_SQLskills_helpindex output you\u2019ll notice that OrderLineID is the only column in columns_in_tree, and both OrderLineID and OrderID_and_OrderLineID are in columns_in_leaf.<\/p>\n
Remember that when you identify a nonclustered index as unique, it will not add the clustering key to the tree level, it just adds it to the leaf level. But if the nonclustered index is not declared as unique, then SQL Server adds the clustering key to the tree level to uniquely identify the row.<\/p>\n
If we had created a clustered index that we didn\u2019t also identify as unique, then SQL Server adds a UNIQUIFIER to the clustered index key, which then also gets added to the nonclustered index.<\/p>\n
Defining the clustering key as part of the non-clustered key<\/h1>\n
What I\u2019ve seen lately when looking at indexes is this:<\/p>\n
\r\nCREATE NONCLUSTERED INDEX [NCI_OrderID_2]     \r\n     ON [Sales].[SQLskills_OrderLines] ([OrderID], [OrderID_and_OrderLineID])\r\n     ON [USERDATA];\r\nGO\r\n<\/pre>\n
This is the same as the NCI_OrderID index I created, but someone has specifically placed the clustering key in the nonclustered index key. I always ask why they added the clustering key. Typically the answer is: I know it\u2019s going to be needed in the query. That\u2019s fine, but understand that it doesn\u2019t matter whether you add the clustering key to the key for a non-unique nonclustered index or not; if you<\/em> don\u2019t, SQL Server will add it.<\/p>\n
We\u2019ve kept it simple so far with a single column for our clustering key. What if we have multiple columns? We\u2019ll change up our table a bit:<\/p>\n
\r\nUSE [WideWorldImporters]\r\nGO\r\n\r\nDROP TABLE IF EXISTS [Sales].[SQLskills_OrderLines];\r\nGO\r\n\r\nCREATE TABLE [Sales].[SQLskills_OrderLines](\r\n     [OrderLineID] [int] NOT NULL,\r\n     [OrderID] [int] NOT NULL,\r\n     [OrderID_and_OrderLineID] [bigint] NOT NULL,\r\n     [StockItemID] [int] NOT NULL,\r\n     [Description] [nvarchar](100) NOT NULL,\r\n     [PackageTypeID] [int] NOT NULL,\r\n     [Quantity] [int] NOT NULL,\r\n     [UnitPrice] [decimal](18, 2) NULL,\r\n     [TaxRate] [decimal](18, 3) NOT NULL,\r\n     [PickedQuantity] [int] NOT NULL,\r\n     [PickingCompletedWhen] [datetime2](7) NULL,\r\n     [LastEditedBy] [int] NOT NULL,\r\n     [LastEditedWhen] [datetime2](7) NOT NULL,\r\n     CONSTRAINT [PK_Sales_SQLskills_OrderLines] PRIMARY KEY CLUSTERED\r\n     (\r\n     [OrderID] ASC, [OrderLineID] ASC, [StockItemID] ASC, [PackageTypeID] ASC\r\n     )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, \r\n     ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [USERDATA]\r\n     ) ON [USERDATA];\r\nGO\r\n\r\nINSERT INTO [Sales].[SQLskills_OrderLines](\r\n     [OrderLineID]\r\n     ,[OrderID]\r\n     ,[OrderID_and_OrderLineID]\r\n     ,[StockItemID]\r\n     ,[Description]\r\n     ,[PackageTypeID]\r\n     ,[Quantity]\r\n     ,[UnitPrice]\r\n     ,[TaxRate]\r\n     ,[PickedQuantity]\r\n     ,[PickingCompletedWhen]\r\n     ,[LastEditedBy]\r\n     ,[LastEditedWhen])\r\nSELECT\r\n     [OrderLineID]\r\n     ,[OrderID]\r\n     ,CAST(CAST([OrderID] AS VARCHAR(20)) + CAST([OrderLineID] AS VARCHAR(20)) AS BIGINT)     \r\n     ,[StockItemID]\r\n     ,[Description]\r\n     ,[PackageTypeID]\r\n     ,[Quantity]\r\n     ,[UnitPrice]\r\n     ,[TaxRate]\r\n     ,[PickedQuantity]\r\n     ,[PickingCompletedWhen]\r\n     ,[LastEditedBy]\r\n     ,[LastEditedWhen]\r\nFROM [Sales].[OrderLines];\r\nGO\r\n\r\nEXEC sp_SQLskills_helpindex 'Sales.SQLskills_OrderLines';\r\nGO\r\n<\/pre>\n
\"Four
Four column clustered index for SQLskills_OrderLines<\/figcaption><\/figure>\n
I don\u2019t generally advocate a wide clustered index, but there are certain scenarios where it\u2019s needed\/appropriate. If we take this table and add a nonclustered index, not unique, on one column, then you\u2019ll see all four columns from the clustering key in the tree level:<\/p>\n
\r\nCREATE NONCLUSTERED INDEX [NCI_Quantity]\r\n     ON [Sales].[SQLskills_OrderLines] ([Quantity])\r\n     ON [USERDATA];\r\nGO\r\n\r\nEXEC sp_SQLskills_helpindex 'Sales.SQLskills_OrderLines';\r\nGO\r\n<\/pre>\n
\"Nonclustered
Nonclustered index (with wide CI) for SQLskills_OrderLines<\/figcaption><\/figure>\n
For a large table, the size of this nonclustered index has the potential to be much, much larger than a table where the clustering key is only a single column.<\/p>\n
If we add a unique nonclustered index, then that clustering key is only in the leaf level:<\/p>\n
\r\nCREATE UNIQUE NONCLUSTERED INDEX [NCI_OrderID_and_OrderLineID]\r\n     ON [Sales].[SQLskills_OrderLines] ([OrderID_and_OrderLineID])\r\n     ON [USERDATA];\r\nGO\r\n\r\nEXEC sp_SQLskills_helpindex 'Sales.SQLskills_OrderLines';\r\nGO\r\n<\/pre>\n
\"Unique
Unique nonclustered index (with wide CI) for SQLskills_OrderLines<\/figcaption><\/figure>\n
But then\u2026what happens if we add one or two columns from the clustering key into the nonclustered index key?<\/p>\n
\r\nCREATE NONCLUSTERED INDEX [NCI_PickingCompletedWhen]\r\n     ON [Sales].[SQLskills_OrderLines] ([PickingCompletedWhen], [OrderID], [OrderLineID])\r\n     ON [USERDATA];\r\nGO\r\n\r\nEXEC sp_SQLskills_helpindex 'Sales.SQLskills_OrderLines';\r\nGO\r\n<\/pre>\n
\"Nonclustered
Nonclustered index with column from clustering key for SQLskills_OrderLines<\/figcaption><\/figure>\n
It doesn\u2019t matter! All the columns from the clustering key are added to the tree level because I did not identify it as unique! If I had defined the nonclustered index as unique, then only those two columns that I specified in the key would be in the tree, and the other two columns from the clustering key would be part of the leaf level.<\/p>\n
Conclusion<\/h1>\n
There are a couple points to remember when designing your nonclustered indexes. First, whenever you know that the column, or combination or columns, makes a unique key for a nonclustered index, I always recommend that you specify UNIQUE when you create the index. That information is great for the optimizer to have when generating query plans. Second, think carefully about the impact of your clustering key on your nonclustered indexes. Any non-unique nonclustered index will be larger (more pages, eventually more levels) because the entire clustering key will be in the tree level. Further, if you happen to have a clustering key with a column (or multiple columns) that are frequently modified, then those modifications have to be propagated to the tree levels of the nonclustered indexes as well.<\/p>\n
Happy indexing!<\/p>\n","protected":false},"excerpt":{"rendered":"
I\u2019ve been helping several customers with tuning lately, which typically means I\u2019m also looking at indexes and asking questions. A pattern I\u2019ve noticed is columns from the clustering key being added to the key definition for the nonclustered index.\u00a0 This brings up some interesting considerations when it comes to creating your nonclustered indexes. Review We\u2019re […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[53,15],"tags":[],"yoast_head":"\nWhat columns are in that index? - Erin Stellato<\/title>\n<meta name=\"description\" content=\"Understanding what columns are in an index is important for mulitple reasons, including understanding how it affects index size and use.\" \/>\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.sqlskills.com\/blogs\/erin\/what-columns-are-in-that-index\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"What columns are in that index? - Erin Stellato\" \/>\n<meta property=\"og:description\" content=\"Understanding what columns are in an index is important for mulitple reasons, including understanding how it affects index size and use.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.sqlskills.com\/blogs\/erin\/what-columns-are-in-that-index\/\" \/>\n<meta property=\"og:site_name\" content=\"Erin Stellato\" \/>\n<meta property=\"article:published_time\" content=\"2019-08-08T13:00:31+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2019-08-08T13:26:07+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.sqlskills.com\/blogs\/erin\/wp-content\/uploads\/2019\/08\/1_CI-1024x36.jpg\" \/>\n<meta name=\"author\" content=\"Erin Stellato\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Erin Stellato\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/erin\/what-columns-are-in-that-index\/\",\"url\":\"https:\/\/www.sqlskills.com\/blogs\/erin\/what-columns-are-in-that-index\/\",\"name\":\"What columns are in that index? - Erin Stellato\",\"isPartOf\":{\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/erin\/#website\"},\"datePublished\":\"2019-08-08T13:00:31+00:00\",\"dateModified\":\"2019-08-08T13:26:07+00:00\",\"author\":{\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/erin\/#\/schema\/person\/76170223ffffa1df03fd9be5b66cb158\"},\"description\":\"Understanding what columns are in an index is important for mulitple reasons, including understanding how it affects index size and use.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/erin\/what-columns-are-in-that-index\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.sqlskills.com\/blogs\/erin\/what-columns-are-in-that-index\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/erin\/what-columns-are-in-that-index\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.sqlskills.com\/blogs\/erin\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"What columns are in that index?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/erin\/#website\",\"url\":\"https:\/\/www.sqlskills.com\/blogs\/erin\/\",\"name\":\"Erin Stellato\",\"description\":\"The SQL Sequel\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.sqlskills.com\/blogs\/erin\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/erin\/#\/schema\/person\/76170223ffffa1df03fd9be5b66cb158\",\"name\":\"Erin Stellato\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/erin\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/0c8b485bd54ea26b57e99f79b525f409?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/0c8b485bd54ea26b57e99f79b525f409?s=96&d=mm&r=g\",\"caption\":\"Erin Stellato\"},\"sameAs\":[\"http:\/\/3.209.169.194\/blogs\/erin\"],\"url\":\"https:\/\/www.sqlskills.com\/blogs\/erin\/author\/erin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"What columns are in that index? - Erin Stellato","description":"Understanding what columns are in an index is important for mulitple reasons, including understanding how it affects index size and use.","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.sqlskills.com\/blogs\/erin\/what-columns-are-in-that-index\/","og_locale":"en_US","og_type":"article","og_title":"What columns are in that index? - Erin Stellato","og_description":"Understanding what columns are in an index is important for mulitple reasons, including understanding how it affects index size and use.","og_url":"https:\/\/www.sqlskills.com\/blogs\/erin\/what-columns-are-in-that-index\/","og_site_name":"Erin Stellato","article_published_time":"2019-08-08T13:00:31+00:00","article_modified_time":"2019-08-08T13:26:07+00:00","og_image":[{"url":"https:\/\/www.sqlskills.com\/blogs\/erin\/wp-content\/uploads\/2019\/08\/1_CI-1024x36.jpg"}],"author":"Erin Stellato","twitter_misc":{"Written by":"Erin Stellato","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.sqlskills.com\/blogs\/erin\/what-columns-are-in-that-index\/","url":"https:\/\/www.sqlskills.com\/blogs\/erin\/what-columns-are-in-that-index\/","name":"What columns are in that index? - Erin Stellato","isPartOf":{"@id":"https:\/\/www.sqlskills.com\/blogs\/erin\/#website"},"datePublished":"2019-08-08T13:00:31+00:00","dateModified":"2019-08-08T13:26:07+00:00","author":{"@id":"https:\/\/www.sqlskills.com\/blogs\/erin\/#\/schema\/person\/76170223ffffa1df03fd9be5b66cb158"},"description":"Understanding what columns are in an index is important for mulitple reasons, including understanding how it affects index size and use.","breadcrumb":{"@id":"https:\/\/www.sqlskills.com\/blogs\/erin\/what-columns-are-in-that-index\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.sqlskills.com\/blogs\/erin\/what-columns-are-in-that-index\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.sqlskills.com\/blogs\/erin\/what-columns-are-in-that-index\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.sqlskills.com\/blogs\/erin\/"},{"@type":"ListItem","position":2,"name":"What columns are in that index?"}]},{"@type":"WebSite","@id":"https:\/\/www.sqlskills.com\/blogs\/erin\/#website","url":"https:\/\/www.sqlskills.com\/blogs\/erin\/","name":"Erin Stellato","description":"The SQL Sequel","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.sqlskills.com\/blogs\/erin\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.sqlskills.com\/blogs\/erin\/#\/schema\/person\/76170223ffffa1df03fd9be5b66cb158","name":"Erin Stellato","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.sqlskills.com\/blogs\/erin\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/0c8b485bd54ea26b57e99f79b525f409?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/0c8b485bd54ea26b57e99f79b525f409?s=96&d=mm&r=g","caption":"Erin Stellato"},"sameAs":["http:\/\/3.209.169.194\/blogs\/erin"],"url":"https:\/\/www.sqlskills.com\/blogs\/erin\/author\/erin\/"}]}},"_links":{"self":[{"href":"https:\/\/www.sqlskills.com\/blogs\/erin\/wp-json\/wp\/v2\/posts\/1032"}],"collection":[{"href":"https:\/\/www.sqlskills.com\/blogs\/erin\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sqlskills.com\/blogs\/erin\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/erin\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/erin\/wp-json\/wp\/v2\/comments?post=1032"}],"version-history":[{"count":0,"href":"https:\/\/www.sqlskills.com\/blogs\/erin\/wp-json\/wp\/v2\/posts\/1032\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.sqlskills.com\/blogs\/erin\/wp-json\/wp\/v2\/media?parent=1032"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/erin\/wp-json\/wp\/v2\/categories?post=1032"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/erin\/wp-json\/wp\/v2\/tags?post=1032"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}