{"id":7772,"date":"2016-04-30T19:27:38","date_gmt":"2016-04-30T17:27:38","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/"},"modified":"2023-07-18T07:45:10","modified_gmt":"2023-07-18T05:45:10","slug":"sql-server-switch-partition-and-metadata-inconsistency-issue","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/","title":{"rendered":"SQL Server: switch partition and metadata inconsistency issue"},"content":{"rendered":"<p>In this blog post, I would like to share with you a weird issue I faced when I implemented a sliding Windows partition scenario on SQL Server 2014 SP1 at one of my customer. The idea was to keep SQL Server audit records from several SQL Server instances into a global archiving table during two years in order to meet the customer audit specifications. Data older than year \u2013 2 should be deleted. Based on a first implementation, we estimated the total data size to 800GB per year.<\/p>\n<p>So we decided to implement the sliding Windows scenario as follows:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-8439 size-full\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-90-01-partition-config-e1462043831475.jpg\" alt=\"blog 90 - 01 - partition config\" width=\"400\" height=\"300\" \/><\/p>\n<ul>\n<li>Right-based partition function is used in this context<\/li>\n<li>Two partitions exist to store current and year \u2013 1 audit data<\/li>\n<li>Partition that contains data older than one year will be switch and then drop<\/li>\n<li>One additional empty partition exists to avoid data movement that may lead to high resource consumption (see my previous blog post <a href=\"http:\/\/dbi-services.com\/blog\/changing-an-existing-partition-configuration-well-not-so-easy\/\" target=\"_blank\" rel=\"noopener noreferrer\">here<\/a>)<\/li>\n<\/ul>\n<p>In addition, we also implemented two stored procedures in order to automate sliding partition process based on the Microsoft article <a href=\"https:\/\/technet.microsoft.com\/en-us\/library\/aa964122(v=sql.90).aspx\" target=\"_blank\" rel=\"noopener noreferrer\">here<\/a>.<\/p>\n<p>And here came the (weird) issue. I always used the following (simplified) script so far to get table information regardless if a table is partitioned or not.<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">SELECT\n\tOBJECT_SCHEMA_NAME(p.object_id) AS SchemaName,\n\tOBJECT_NAME(p.object_id) AS ObjectName,\n\ti.name as index_name,\n\ti.index_id,\n    p.partition_number,\n    g.name AS [filegroup_name],\n\tau.data_space_id,\n    p.rows,\n\tp.data_compression_desc\nFROM sys.partitions AS p\nJOIN sys.allocation_units AS au\n    ON au.container_id = p.partition_id -- p.hobt_id \nJOIN sys.indexes i\n\tON p.object_id = i.object_id\n    AND p.index_id = i.index_id\nJOIN sys.filegroups AS g\n    ON g.data_space_id = au.data_space_id\nWHERE p.object_id = object_id('dbo.t_sql_logins')\n       AND p.index_id = 1;\nGO<\/pre>\n<p>Here the output of the initial scenario in my case:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-8440\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-90-02-partition-info-initial-scenario.jpg\" alt=\"blog 90 - 02 - partition info initial scenario\" width=\"811\" height=\"77\" \/><\/p>\n<p>Let\u2019s say that the partition 1 contains Year-1 data.\u00a0 Si I included this query to detect dynamically which partition to switch inside the stored procedure that deals with the left side of the partitioned table (that includes switch and merge operations) and this is exactly where the problem occurs.<\/p>\n<p>The new scenario is as follows:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-8441\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-90-02-partition-info-after-switching-scenario.jpg\" alt=\"blog 90 - 02 - partition info after switching scenario\" width=\"813\" height=\"79\" \/><\/p>\n<p>After switching the old partition and then merge the existing left boundary, I noticed metadata inconsistency regarding the following error message. In short, this message indicates my query doesn\u2019t detect correctly which partition hosts data to delete because it seems to not be correctly aligned with archive table. They are not on the same filegroup.<\/p>\n<p><em>ALTER TABLE SWITCH statement failed. index &#8216;security_audit.dbo.test_archive.PK_test_archive&#8217; is in filegroup &#8216;FG_AUDIT_SQL_03&#8217; and partition 1 of index &#8216;security_audit.dbo.test.PK_test&#8217; is in filegroup &#8216;FG_AUDIT_SQL_02&#8217;<\/em><\/p>\n<p>Fortunately, <a href=\"http:\/\/weblogs.sqlteam.com\/dang\/\" target=\"_blank\" rel=\"noopener noreferrer\">Dan Guzman<\/a> (MVP Data Platform) puts me on the right track with the following query:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">SELECT \n\tOBJECT_SCHEMA_NAME(p.object_id) AS SchemaName\n\t, OBJECT_NAME(p.object_id) AS ObjectName\n\t, i.name AS IndexName\n\t, p.index_id AS IndexID\n\t, p.partition_number AS PartitionNumber\n\t, fg2.name AS FileGroupName\n\t, fg2.data_space_id\n\t, p.rows AS Rows\n\t, p.data_compression_desc\nFROM sys.partitions AS p\nINNER JOIN sys.indexes AS i \n\tON i.object_id = p.object_id\n\tAND i.index_id = p.index_id\nINNER JOIN sys.data_spaces AS ds \n\tON ds.data_space_id = i.data_space_id\nINNER JOIN sys.partition_schemes AS ps \n\tON ps.data_space_id = ds.data_space_id\nINNER JOIN sys.partition_functions AS pf \n\tON pf.function_id = ps.function_id\nINNER JOIN sys.destination_data_spaces AS dds2 \n\tON dds2.partition_scheme_id = ps.data_space_id\n\tAND dds2.destination_id = p.partition_number\nINNER JOIN sys.filegroups AS fg2 \n\tON fg2.data_space_id = dds2.data_space_id\nWHERE p.object_id in ( object_id('dbo.t_sql_logins') )\n\tAND P.index_id = 1<\/pre>\n<p>You may notice that the output is not pretty the same than the previous query.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-8442\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-90-03-partition-info-after-switching-scenario-correct.jpg\" alt=\"blog 90 - 03 - partition info after switching scenario correct\" width=\"813\" height=\"79\" \/><\/p>\n<p>This time the partition number 1 seems to be more accurate with the FG_AUDIT_SQL_03 value. So why this difference between the two queries? If we take a further look at the both queries, we may see a noticeable difference with the use of <em>sys.allocation_units<\/em> DMV in the first query versus <em>sys.destination_data_spaces<\/em> DMV in the second one.<\/p>\n<p>Let\u2019s divide and simplify the above queries into small pieces and let\u2019s have a look at the following result:<\/p>\n<pre class=\"brush: sql; gutter: true; first-line: 1\">SELECT \n\tpartition_id,\n\tpartition_number,\n\thobt_id\nFROM sys.partitions \nWHERE object_id in ( object_id('dbo.t_sql_logins') );\n\nSELECT \n\tallocation_unit_id,\n\tcontainer_id,\n\tdata_space_id\nFROM sys.allocation_units \nWHERE container_id IN ( 72057594040811520, 72057594040877056, 72057594041073664);\n\nSELECT \n\tname,\n\tdata_space_id\nFROM sys.filegroups;\n\nSELECT \n\tdestination_id,\n\tdata_space_id\nFROM sys.destination_data_spaces;<\/pre>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-8443\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-90-04-partition-info-difference-DMVs.jpg\" alt=\"blog 90 - 04 - partition info difference DMVs\" width=\"450\" height=\"364\" \/><\/p>\n<p>Red arrows concern the first query and the green arrows concern the second one. \u00a0The arrows represent the value used for joining DMVs together. You may notice the filegroup name is different between the both queries which makes me think that the <em>data_space_id<\/em> value from the <em>sys.allocation_units<\/em> DMV is inconsistent in this case. In addition, we may notice two same <em>data_space_id<\/em> column values for each different value of <em>container_id<\/em>. The point here is that if I rebuild the corresponding index, this inconsistency disappears as shown below:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-8444\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-90-05-partition-info-correct-result-DMVs.jpg\" alt=\"blog 90 - 05 - partition info correct result DMVs\" width=\"420\" height=\"364\" \/><\/p>\n<p>After further investigations, I found out the following Microsoft <a href=\"https:\/\/support.microsoft.com\/en-us\/kb\/3095958\" target=\"_blank\" rel=\"noopener noreferrer\">KB3095958<\/a> that talks about metadata inconsistency after a partition switch and SQL Server 2014 SP1. Applying this KB on my environment fixed this specific issue in my case.<\/p>\n<p>Happy partitioning!<\/p>\n<p>By David Barbarin<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In this blog post, I would like to share with you a weird issue I faced when I implemented a sliding Windows partition scenario on SQL Server 2014 SP1 at one of my customer. The idea was to keep SQL Server audit records from several SQL Server instances into a global archiving table during two [&hellip;]<\/p>\n","protected":false},"author":26,"featured_media":7779,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[828,752,366,51,52,754],"type_dbi":[],"class_list":["post-7772","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-database-administration-monitoring","tag-inconsistency","tag-merge","tag-partitioning","tag-sql-server","tag-sql-server-2014","tag-switch"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>SQL Server: switch partition and metadata inconsistency issue<\/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.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SQL Server: switch partition and metadata inconsistency issue\" \/>\n<meta property=\"og:description\" content=\"In this blog post, I would like to share with you a weird issue I faced when I implemented a sliding Windows partition scenario on SQL Server 2014 SP1 at one of my customer. The idea was to keep SQL Server audit records from several SQL Server instances into a global archiving table during two [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2016-04-30T17:27:38+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-07-18T05:45:10+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-90-01-partition-config-e1462043831475-1.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"400\" \/>\n\t<meta property=\"og:image:height\" content=\"300\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Microsoft Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Microsoft Team\" \/>\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.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/\"},\"author\":{\"name\":\"Microsoft Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4\"},\"headline\":\"SQL Server: switch partition and metadata inconsistency issue\",\"datePublished\":\"2016-04-30T17:27:38+00:00\",\"dateModified\":\"2023-07-18T05:45:10+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/\"},\"wordCount\":611,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-90-01-partition-config-e1462043831475-1.jpg\",\"keywords\":[\"inconsistency\",\"MERGE\",\"Partitioning\",\"SQL Server\",\"SQL Server 2014\",\"SWITCH\"],\"articleSection\":[\"Database Administration &amp; Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/\",\"name\":\"SQL Server: switch partition and metadata inconsistency issue\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-90-01-partition-config-e1462043831475-1.jpg\",\"datePublished\":\"2016-04-30T17:27:38+00:00\",\"dateModified\":\"2023-07-18T05:45:10+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/#primaryimage\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-90-01-partition-config-e1462043831475-1.jpg\",\"contentUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-90-01-partition-config-e1462043831475-1.jpg\",\"width\":400,\"height\":300},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SQL Server: switch partition and metadata inconsistency issue\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4\",\"name\":\"Microsoft Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g\",\"caption\":\"Microsoft Team\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/microsoft-team\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"SQL Server: switch partition and metadata inconsistency issue","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.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/","og_locale":"en_US","og_type":"article","og_title":"SQL Server: switch partition and metadata inconsistency issue","og_description":"In this blog post, I would like to share with you a weird issue I faced when I implemented a sliding Windows partition scenario on SQL Server 2014 SP1 at one of my customer. The idea was to keep SQL Server audit records from several SQL Server instances into a global archiving table during two [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/","og_site_name":"dbi Blog","article_published_time":"2016-04-30T17:27:38+00:00","article_modified_time":"2023-07-18T05:45:10+00:00","og_image":[{"width":400,"height":300,"url":"http:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-90-01-partition-config-e1462043831475-1.jpg","type":"image\/jpeg"}],"author":"Microsoft Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Microsoft Team","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/"},"author":{"name":"Microsoft Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4"},"headline":"SQL Server: switch partition and metadata inconsistency issue","datePublished":"2016-04-30T17:27:38+00:00","dateModified":"2023-07-18T05:45:10+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/"},"wordCount":611,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-90-01-partition-config-e1462043831475-1.jpg","keywords":["inconsistency","MERGE","Partitioning","SQL Server","SQL Server 2014","SWITCH"],"articleSection":["Database Administration &amp; Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/","url":"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/","name":"SQL Server: switch partition and metadata inconsistency issue","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-90-01-partition-config-e1462043831475-1.jpg","datePublished":"2016-04-30T17:27:38+00:00","dateModified":"2023-07-18T05:45:10+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-90-01-partition-config-e1462043831475-1.jpg","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-90-01-partition-config-e1462043831475-1.jpg","width":400,"height":300},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-switch-partition-and-metadata-inconsistency-issue\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"SQL Server: switch partition and metadata inconsistency issue"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4","name":"Microsoft Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g","caption":"Microsoft Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/microsoft-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/7772","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/26"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=7772"}],"version-history":[{"count":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/7772\/revisions"}],"predecessor-version":[{"id":26810,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/7772\/revisions\/26810"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/7779"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=7772"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=7772"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=7772"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=7772"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}