{"id":503,"date":"2012-03-08T02:32:00","date_gmt":"2012-03-08T02:32:00","guid":{"rendered":"\/blogs\/joe\/post\/Comparing-Query-Performance-when-using-an-e2809cideale2809d-Nonclustered-Index-versus-Columnstore-Index.aspx"},"modified":"2013-01-02T20:32:16","modified_gmt":"2013-01-03T04:32:16","slug":"comparing-query-performance-when-using-an-ideal-nonclustered-index-versus-columnstore-index","status":"publish","type":"post","link":"https:\/\/www.sqlskills.com\/blogs\/joe\/comparing-query-performance-when-using-an-ideal-nonclustered-index-versus-columnstore-index\/","title":{"rendered":"Comparing Query Performance when using an \u201cideal\u201d Nonclustered Index versus Columnstore Index"},"content":{"rendered":"

I gave a presentation on columnstore indexing last week and one question I received was regarding the performance of a (hypothetical) narrow, supporting nonclustered index versus a columnstore index.  <\/span>We discussed how nonclustered indexes were still going to be more effective for specific types of queries (for example \u2013 singleton operations, smaller range scans, etc.).  <\/span>But what about a situation where we\u2019re aggregating data across the entire fact table? Was there any way that a narrow nonclustered index could measure up against a columnstore index?<\/font><\/font><\/p>\n

The ability to contrast the performance is of course very much dependent on the query construction, table design, data distribution and other factors.  <\/span>With that said, I thought I would test out a scenario as follows\u2026<\/font><\/font><\/p>\n

First of all, I used FactInternetSales – pumped up to 123,695,104 rows.  <\/span>The query I used for comparing performance was as follows (with a few hint-modifications to force index and parallelism caps that I used later):<\/font><\/font><\/p>\n

SELECT<\/font><\/font><\/span>     <\/span>p<\/font><\/span>.<\/font><\/span>ProductLine<\/font><\/span><\/font>,<\/font><\/span><\/span><\/font><\/p>\n

           <\/font><\/span>SUM<\/font><\/span>(<\/font><\/span>f<\/font><\/span>.<\/font><\/span>SalesAmount<\/font><\/span>)<\/font><\/span> <\/font>TotalSalesAmount<\/font><\/span><\/font><\/span><\/p>\n

FROM<\/font><\/font><\/span> [dbo]<\/font><\/span>.<\/font><\/span>[FactInternetSales]<\/font><\/span> <\/font>f<\/font><\/span><\/span><\/font><\/p>\n

INNER<\/font><\/font><\/span> JOIN<\/font><\/span> [dbo]<\/font><\/span>.<\/font><\/span>[DimProduct]<\/font><\/span> p<\/font><\/span> <\/font>ON<\/font><\/span><\/span><\/font><\/p>\n

     <\/font><\/span>f<\/font><\/span>.<\/font><\/span>ProductKey<\/font><\/span> =<\/font><\/span> p<\/font><\/span>.<\/font><\/span><\/font>ProductKey<\/font><\/span><\/font><\/span><\/p>\n

GROUP<\/font><\/font><\/span> BY<\/font><\/span> p<\/font><\/span>.<\/font><\/span><\/font>ProductLine<\/font><\/span><\/span><\/font><\/p>\n

ORDER<\/font><\/font><\/span> BY<\/font><\/span> p<\/font><\/span>.<\/font><\/span>ProductLine<\/font><\/span><\/font>;<\/font><\/span><\/span><\/font><\/p>\n

 <\/font><\/font><\/p>\n

I created the following nonclustered indexes (index on joining keys \u2013 and then an INCLUDE on the SalesAmount which is being aggregated):<\/font><\/font><\/p>\n

CREATE<\/font><\/font><\/span> NONCLUSTERED<\/font><\/span> INDEX<\/font><\/span> [NCI_FactInternetSales_ProductKey]<\/font><\/span> <\/font><\/span><\/font><\/p>\n

ON<\/font><\/font><\/span> [dbo]<\/font><\/span>.<\/font><\/span><\/font>[FactInternetSales]<\/font><\/span><\/span><\/font><\/p>\n

(<\/font><\/font><\/span>[ProductKey]<\/font><\/span><\/font> ASC<\/font><\/span><\/font>)<\/font><\/span><\/span><\/font><\/p>\n

INCLUDE <\/font><\/font><\/span>(<\/font><\/span><\/font> <\/span>[SalesAmount]<\/font><\/span>)<\/font><\/span> ON<\/font><\/span> [PRIMARY]<\/font><\/span><\/font>;<\/font><\/span><\/span><\/font><\/p>\n

GO<\/font><\/font><\/span><\/span><\/p>\n

 <\/font><\/font><\/span><\/p>\n

CREATE<\/font><\/font><\/span> NONCLUSTERED<\/font><\/span> INDEX<\/font><\/span> [NCI_DimProduct_ProductKey_ProductLine]<\/font><\/span> ON<\/font><\/span> [dbo]<\/font><\/span>.<\/font><\/span><\/font>[DimProduct]<\/font><\/span><\/span><\/font><\/p>\n

(<\/font><\/font><\/span>    <\/span>[ProductKey]<\/font><\/span> ASC<\/font><\/span><\/font>,<\/font><\/span><\/span><\/font><\/p>\n

     <\/font><\/span>[ProductLine]<\/font><\/span> <\/font>ASC<\/font><\/span><\/font><\/span><\/p>\n

)<\/font><\/font><\/span>ON<\/font><\/span><\/font> [PRIMARY]<\/font><\/span><\/font>;<\/font><\/span><\/span><\/font><\/p>\n

GO<\/font><\/font><\/span><\/p>\n

 <\/font><\/font><\/p>\n

I also created a columnstore index that covered all columns in the fact table.  <\/span>To force my query to ignore that index for the comparison test, I added the following line:<\/font><\/font><\/p>\n

OPTION <\/font><\/font><\/span>(<\/font><\/span>IGNORE_NONCLUSTERED_COLUMNSTORE_INDEX<\/font><\/span><\/font>);<\/font><\/span><\/font><\/p>\n

 <\/font><\/font><\/p>\n

So how did the performance compare between a supporting nonclustered index versus the columnstore index? (By the way, I used a warm cache for both tests \u2013 executing twice<\/i>):<\/font><\/font><\/p>\n\n\n\n\n\n
\n

Index Support<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n

\n

Elapsed Time<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n

\n

CPU Time<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n<\/tr>\n

\n

Columnstore<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n

\n

256 ms.<\/font><\/font><\/span><\/p>\n<\/td>\n

\n

1045 ms.<\/font><\/font><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

Nonclustered index<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n

\n

34189 ms.<\/font><\/font><\/span><\/p>\n<\/td>\n

\n

33322 ms<\/font><\/font><\/span><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/font><\/font><\/p>\n

The columnstore index plan was as follows:<\/font><\/font><\/p>\n

\"clip_image002\"<\/a><\/span><\/p>\n

The nonclustered index plan was as follows:<\/font><\/font><\/p>\n

\"clip_image004\"<\/a><\/span><\/p>\n

One obvious difference is that the columnstore index execution leveraged parallelism.  <\/span>The query also benefited from batch execution mode:<\/font><\/font><\/p>\n

\"clip_image006\"<\/a><\/span><\/p>\n

If I hobble the columnstore index by capping max degree of parallelism, the results (in comparison) are as follows (third row represents the test):<\/font><\/font><\/p>\n\n\n\n\n\n\n
\n

Intended Index Support<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n

\n

Elapsed Time<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n

\n

CPU Time<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n

\n

Mode<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n<\/tr>\n

\n

Columnstore<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n

\n

256 ms.<\/font><\/font><\/span><\/p>\n<\/td>\n

\n

1045 ms.<\/font><\/font><\/span><\/p>\n<\/td>\n

\n

Batch<\/font><\/font><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

Nonclustered index<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n

\n

34189 ms.<\/font><\/font><\/span><\/p>\n<\/td>\n

\n

33322 ms.<\/font><\/font><\/span><\/p>\n<\/td>\n

\n

Row<\/font><\/font><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

Columnstore index (MAXDOP 1) \u2013 <\/font>ending up using NCI<\/font><\/i><\/font><\/span><\/b><\/p>\n<\/td>\n

\n

33540 ms.<\/font><\/font><\/span><\/p>\n<\/td>\n

\n

34560 ms.<\/font><\/font><\/span><\/p>\n<\/td>\n

\n

Row<\/font><\/font><\/span><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/font><\/font><\/p>\n

Looking at the plan, we see the columnstore index wasn\u2019t used at all:<\/font><\/font><\/p>\n

\"clip_image008\"<\/a><\/span><\/p>\n

If I force use of the columnstore index with MAXDOP 1, I see:<\/font><\/font><\/p>\n\n\n\n\n\n\n\n
\n

Index Support<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n

\n

Elapsed Time<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n

\n

CPU Time<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n

\n

Mode<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n<\/tr>\n

\n

Columnstore<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n

\n

256 ms.<\/font><\/font><\/span><\/p>\n<\/td>\n

\n

1045 ms.<\/font><\/font><\/span><\/p>\n<\/td>\n

\n

Batch<\/font><\/font><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

Nonclustered index<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n

\n

34189 ms.<\/font><\/font><\/span><\/p>\n<\/td>\n

\n

33322 ms.<\/font><\/font><\/span><\/p>\n<\/td>\n

\n

Row<\/font><\/font><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

Columnstore index (MAXDOP 1) \u2013 ending up using NCI<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n

\n

33540 ms.<\/font><\/font><\/span><\/p>\n<\/td>\n

\n

34560 ms.<\/font><\/font><\/span><\/p>\n<\/td>\n

\n

Row<\/font><\/font><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

Columnstore index (MAXDOP 1) \u2013 forced <\/i>columnstore index<\/font><\/font><\/span><\/b><\/p>\n<\/td>\n

\n

29859 ms.<\/font><\/font><\/span><\/p>\n<\/td>\n

\n

30107 ms.<\/font><\/font><\/span><\/p>\n<\/td>\n

\n

Row<\/font><\/font><\/span><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/font><\/font><\/p>\n

The plan shows the index is used, but it is row mode (due to capping parallelism):<\/font><\/font><\/p>\n

\"clip_image010\"<\/a><\/span><\/p>\n

\"clip_image012\"<\/a><\/span><\/p>\n

Looping back to the inciting discussion \u2013 even with a supporting nonclustered index, this specific query which scanned all 123 million rows and returned a smaller result set with aggregated values performed significantly better when using a columnstore index in conjunction with<\/i> batch execution mode. <\/font><\/font><\/p>\n","protected":false},"excerpt":{"rendered":"

I gave a presentation on columnstore indexing last week and one question I received was regarding the performance of a (hypothetical) narrow, supporting nonclustered index versus a columnstore index.  We discussed how nonclustered indexes were still going to be more effective for specific types of queries (for example \u2013 singleton operations, smaller range scans, etc.).  […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[28],"tags":[],"class_list":["post-503","post","type-post","status-publish","format-standard","hentry","category-performance"],"yoast_head":"\nComparing Query Performance when using an \u201cideal\u201d Nonclustered Index versus Columnstore Index - Joe Sack<\/title>\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\/joe\/comparing-query-performance-when-using-an-ideal-nonclustered-index-versus-columnstore-index\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Comparing Query Performance when using an \u201cideal\u201d Nonclustered Index versus Columnstore Index - Joe Sack\" \/>\n<meta property=\"og:description\" content=\"I gave a presentation on columnstore indexing last week and one question I received was regarding the performance of a (hypothetical) narrow, supporting nonclustered index versus a columnstore index.  We discussed how nonclustered indexes were still going to be more effective for specific types of queries (for example \u2013 singleton operations, smaller range scans, etc.).  […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.sqlskills.com\/blogs\/joe\/comparing-query-performance-when-using-an-ideal-nonclustered-index-versus-columnstore-index\/\" \/>\n<meta property=\"og:site_name\" content=\"Joe Sack\" \/>\n<meta property=\"article:published_time\" content=\"2012-03-08T02:32:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2013-01-03T04:32:16+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.sqlskills.com\/blogs\/joe\/wp-content\/uploads\/windows-live-writer\/comparing-query-performance-when-using-a\/3212f805\/clip_image002_thumb.jpg\" \/>\n<meta name=\"author\" content=\"Joseph Sack\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Joseph Sack\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/joe\/comparing-query-performance-when-using-an-ideal-nonclustered-index-versus-columnstore-index\/\",\"url\":\"https:\/\/www.sqlskills.com\/blogs\/joe\/comparing-query-performance-when-using-an-ideal-nonclustered-index-versus-columnstore-index\/\",\"name\":\"Comparing Query Performance when using an \u201cideal\u201d Nonclustered Index versus Columnstore Index - Joe Sack\",\"isPartOf\":{\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/joe\/#website\"},\"datePublished\":\"2012-03-08T02:32:00+00:00\",\"dateModified\":\"2013-01-03T04:32:16+00:00\",\"author\":{\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/joe\/#\/schema\/person\/533eb0113a15fb5a6e8067a49e4ae648\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/joe\/comparing-query-performance-when-using-an-ideal-nonclustered-index-versus-columnstore-index\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.sqlskills.com\/blogs\/joe\/comparing-query-performance-when-using-an-ideal-nonclustered-index-versus-columnstore-index\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/joe\/comparing-query-performance-when-using-an-ideal-nonclustered-index-versus-columnstore-index\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.sqlskills.com\/blogs\/joe\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Performance\",\"item\":\"https:\/\/www.sqlskills.com\/blogs\/joe\/category\/performance\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Comparing Query Performance when using an \u201cideal\u201d Nonclustered Index versus Columnstore Index\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/joe\/#website\",\"url\":\"https:\/\/www.sqlskills.com\/blogs\/joe\/\",\"name\":\"Joe Sack\",\"description\":\"SQL Server Performance Tuning, High Availability and Disaster Recovery Blog\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.sqlskills.com\/blogs\/joe\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/joe\/#\/schema\/person\/533eb0113a15fb5a6e8067a49e4ae648\",\"name\":\"Joseph Sack\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/joe\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/a4b39a7719a6bfff1add3ec00527810734579ee114d6d983e8e68f937b77be96?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/a4b39a7719a6bfff1add3ec00527810734579ee114d6d983e8e68f937b77be96?s=96&d=mm&r=g\",\"caption\":\"Joseph Sack\"},\"description\":\"Joe Sack is a Principal Consultant with SQLskills. He has worked as a SQL Server professional since 1997 and has supported and developed for SQL Server environments in financial services, IT consulting, manufacturing, retail and the real estate industry. Prior to joining SQLskills he worked at Microsoft as a Premier Field Engineer supporting very large enterprise customer environments. He was responsible for providing deep SQL Server advisory services, training, troubleshooting and ongoing solutions guidance. His areas of expertise include performance tuning, scalability, T-SQL development and high-availability. In 2006 Joe earned the \u201cMicrosoft Certified Master: SQL Server 2005\u201d certification and in 2008 he earned the \u201cMicrosoft Certified Master: SQL Server 2008\u201d certification. In 2009 he took over responsibility for the entire SQL Server Microsoft Certified Master program and held that post until 2011. He was given the SQL Server MVP award in 2013.\",\"sameAs\":[\"http:\/\/3.209.169.194\/blogs\/joe\",\"https:\/\/twitter.com\/https:\/\/twitter.com\/josephsack\"],\"url\":\"https:\/\/www.sqlskills.com\/blogs\/joe\/author\/joe\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Comparing Query Performance when using an \u201cideal\u201d Nonclustered Index versus Columnstore Index - Joe Sack","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\/joe\/comparing-query-performance-when-using-an-ideal-nonclustered-index-versus-columnstore-index\/","og_locale":"en_US","og_type":"article","og_title":"Comparing Query Performance when using an \u201cideal\u201d Nonclustered Index versus Columnstore Index - Joe Sack","og_description":"I gave a presentation on columnstore indexing last week and one question I received was regarding the performance of a (hypothetical) narrow, supporting nonclustered index versus a columnstore index.  We discussed how nonclustered indexes were still going to be more effective for specific types of queries (for example \u2013 singleton operations, smaller range scans, etc.).  […]","og_url":"https:\/\/www.sqlskills.com\/blogs\/joe\/comparing-query-performance-when-using-an-ideal-nonclustered-index-versus-columnstore-index\/","og_site_name":"Joe Sack","article_published_time":"2012-03-08T02:32:00+00:00","article_modified_time":"2013-01-03T04:32:16+00:00","og_image":[{"url":"https:\/\/www.sqlskills.com\/blogs\/joe\/wp-content\/uploads\/windows-live-writer\/comparing-query-performance-when-using-a\/3212f805\/clip_image002_thumb.jpg"}],"author":"Joseph Sack","twitter_misc":{"Written by":"Joseph Sack","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.sqlskills.com\/blogs\/joe\/comparing-query-performance-when-using-an-ideal-nonclustered-index-versus-columnstore-index\/","url":"https:\/\/www.sqlskills.com\/blogs\/joe\/comparing-query-performance-when-using-an-ideal-nonclustered-index-versus-columnstore-index\/","name":"Comparing Query Performance when using an \u201cideal\u201d Nonclustered Index versus Columnstore Index - Joe Sack","isPartOf":{"@id":"https:\/\/www.sqlskills.com\/blogs\/joe\/#website"},"datePublished":"2012-03-08T02:32:00+00:00","dateModified":"2013-01-03T04:32:16+00:00","author":{"@id":"https:\/\/www.sqlskills.com\/blogs\/joe\/#\/schema\/person\/533eb0113a15fb5a6e8067a49e4ae648"},"breadcrumb":{"@id":"https:\/\/www.sqlskills.com\/blogs\/joe\/comparing-query-performance-when-using-an-ideal-nonclustered-index-versus-columnstore-index\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.sqlskills.com\/blogs\/joe\/comparing-query-performance-when-using-an-ideal-nonclustered-index-versus-columnstore-index\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.sqlskills.com\/blogs\/joe\/comparing-query-performance-when-using-an-ideal-nonclustered-index-versus-columnstore-index\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.sqlskills.com\/blogs\/joe\/"},{"@type":"ListItem","position":2,"name":"Performance","item":"https:\/\/www.sqlskills.com\/blogs\/joe\/category\/performance\/"},{"@type":"ListItem","position":3,"name":"Comparing Query Performance when using an \u201cideal\u201d Nonclustered Index versus Columnstore Index"}]},{"@type":"WebSite","@id":"https:\/\/www.sqlskills.com\/blogs\/joe\/#website","url":"https:\/\/www.sqlskills.com\/blogs\/joe\/","name":"Joe Sack","description":"SQL Server Performance Tuning, High Availability and Disaster Recovery Blog","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.sqlskills.com\/blogs\/joe\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.sqlskills.com\/blogs\/joe\/#\/schema\/person\/533eb0113a15fb5a6e8067a49e4ae648","name":"Joseph Sack","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.sqlskills.com\/blogs\/joe\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/a4b39a7719a6bfff1add3ec00527810734579ee114d6d983e8e68f937b77be96?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/a4b39a7719a6bfff1add3ec00527810734579ee114d6d983e8e68f937b77be96?s=96&d=mm&r=g","caption":"Joseph Sack"},"description":"Joe Sack is a Principal Consultant with SQLskills. He has worked as a SQL Server professional since 1997 and has supported and developed for SQL Server environments in financial services, IT consulting, manufacturing, retail and the real estate industry. Prior to joining SQLskills he worked at Microsoft as a Premier Field Engineer supporting very large enterprise customer environments. He was responsible for providing deep SQL Server advisory services, training, troubleshooting and ongoing solutions guidance. His areas of expertise include performance tuning, scalability, T-SQL development and high-availability. In 2006 Joe earned the \u201cMicrosoft Certified Master: SQL Server 2005\u201d certification and in 2008 he earned the \u201cMicrosoft Certified Master: SQL Server 2008\u201d certification. In 2009 he took over responsibility for the entire SQL Server Microsoft Certified Master program and held that post until 2011. He was given the SQL Server MVP award in 2013.","sameAs":["http:\/\/3.209.169.194\/blogs\/joe","https:\/\/twitter.com\/https:\/\/twitter.com\/josephsack"],"url":"https:\/\/www.sqlskills.com\/blogs\/joe\/author\/joe\/"}]}},"_links":{"self":[{"href":"https:\/\/www.sqlskills.com\/blogs\/joe\/wp-json\/wp\/v2\/posts\/503","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sqlskills.com\/blogs\/joe\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sqlskills.com\/blogs\/joe\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/joe\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/joe\/wp-json\/wp\/v2\/comments?post=503"}],"version-history":[{"count":0,"href":"https:\/\/www.sqlskills.com\/blogs\/joe\/wp-json\/wp\/v2\/posts\/503\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.sqlskills.com\/blogs\/joe\/wp-json\/wp\/v2\/media?parent=503"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/joe\/wp-json\/wp\/v2\/categories?post=503"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/joe\/wp-json\/wp\/v2\/tags?post=503"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}