{"id":3621,"date":"2012-05-24T11:07:35","date_gmt":"2012-05-24T10:07:35","guid":{"rendered":"http:\/\/blog.capdata.fr\/?p=3621"},"modified":"2022-12-19T09:30:34","modified_gmt":"2022-12-19T08:30:34","slug":"sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed","status":"publish","type":"post","link":"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/","title":{"rendered":"[sqsrvres] OnlineThread: SQL Cluster shared data upgrade failed"},"content":{"rendered":"\"twitter\"<\/a>\"linkedin\"<\/a>\"mail\"<\/a>

Hello,<\/p>\n

Il existe d\u00e9j\u00e0 un post sur ce probl\u00e8me sp\u00e9cifique au patch de cluster\u00a0 SQL Server 2008 \/ 2008R2 ici<\/a>, mais je suis tomb\u00e9 dessus ce matin et je me disais qu’il serait pas mal de poster un peu les \u00e9tapes de r\u00e9solution en fran\u00e7ais.<\/p>\n

Le probl\u00e8me se pose lorsque l’on patche un SQL Server 2008 ou 2008 R2 dans un cluster WFC Windows 2008 \/ 2008R2. Contrairement au patch sur windows 2003, o\u00f9 le setup \u00e9tait lanc\u00e9 sur le n\u0153ud actif et cr\u00e9ait des t\u00e2ches planifi\u00e9es sur les n\u0153uds distants, le mode de patch a \u00e9t\u00e9 revu \u00e0 partir de Windows 2008 et la proc\u00e9dure est devenue :<\/p>\n

– Patch du noeud inactif.
\n– Reboot du noeud inactif.
\n– Bascule du groupe SQL Server sur le nouveau noeud.
\n– Patch du noeud inactif.
\n– Reboot du noeud inactif.
\n– Rebascule en mode nominal.<\/em><\/p>\n

Ce mode a plusieurs avantages: d’abord la disponibilit\u00e9, puisque pendant que le patch est d\u00e9pos\u00e9 sur le noeud inactif, SQL Server est toujours up and running sur le noeud actif. L’instance sera r\u00e9ellement upgrad\u00e9e lors de la bascule. Ensuite, un retour arri\u00e8re plus ais\u00e9 dans la mesure o\u00f9 il suffit de downgrader le noeud inactif, sans coupure de production.<\/p>\n

Le probl\u00e8me se pose lors de la bascule, et donc \u00e0 l’\u00e9tape ou SQL Server est red\u00e9marr\u00e9 \u00e0 travers le gestionnaire du cluster: dans l’event viewer, l’erreur \u00e9ponyme:<\/p>\n

[sqsrvres] OnlineThread: SQL Cluster shared data upgrade failed<\/span><\/pre>\n
A partir de l\u00e0, on ne verra rien de particulier dans l’ERRORLOG, l’instance est d\u00e9marr\u00e9e en RTM, puis stopp\u00e9e par le gestionnaire de services. Il faut aller jeter un coup d\u2019\u0153il au log du cluster. Par d\u00e9faut ce log se trouve sous C:\\Windows\\Cluster\\Reports\\Cluster.log. S’il n’existe pas, il suffit de le cr\u00e9er dans un elevated prompt:<\/p>\n
Microsoft Windows [Version 6.1.7601]\r\nCopyright (c) 2009 Microsoft Corporation.\u00a0 All rights reserved.\r\n\r\nC:\\Users\\sqlcluadmin>cluster log \/g\r\nGenerating the cluster log(s) ...\r\nThe cluster log has been successfully generated on node 'node1'...\r\nThe cluster log has been successfully generated on node 'node2'...<\/pre>\n
Pour en savoir un peu plus, il faudra aussi activer le mode Verbose pour la ressource SQL Server, en passant la cl\u00e9\u00a0 HKLM\\Cluster\\Resources\\<ID de la ressource SQL>\\Parameters\\VerboseLogging <\/em>\u00e0 1<\/em><\/p>\n
<\/p>\n
Puis relancer la mise en ligne de la ressource SQL Server pour pouvoir constater l’erreur dans la log:<\/p>\n
(...)\r\n05\/24-09:07:43.951 INFO\u00a0 [RCM] TransitionToState(SQL Server) OnlineCallIssued-->OnlinePending.\r\n00001bf0.00000c68::2012\/05\/24-09:07:43.951 INFO\u00a0 [RES] SQL Server <SQL Server>: [sqsrvres] OnlineThread: enter; VirtualServerName=MYMSSQLSERVER2; InstanceName=MSSQLSERVER\r\n00001bf0.00000c68::2012\/05\/24-09:07:43.951 INFO\u00a0 [RES] SQL Server <SQL Server>: [sqsrvres] OnlineThread: ServiceName=MSSQLSERVER\r\n00001bf0.00000c68::2012\/05\/24-09:07:43.951 INFO\u00a0 [RES] SQL Server <SQL Server>: [sqsrvres] ClusterResourceControl, found the network name: MYMSSQLSERVER2.\r\n00001bf0.00000c68::2012\/05\/24-09:07:43.951 INFO\u00a0 [RES] SQL Server <SQL Server>: [sqsrvres] OnlineThread: ServerName=MYMSSQLSERVER2\r\n00001bf0.00000c68::2012\/05\/24-09:07:43.951 INFO\u00a0 [RES] SQL Server <SQL Server>: [sqsrvres] Worker Thread (A497A0): Calling SQLClusterResourceWorker::WaitForCompletion (200)\r\n00001bf0.00001cac::2012\/05\/24-09:07:43.951 INFO\u00a0 [RES] SQL Server <SQL Server>: [sqsrvres] Worker Thread (A497A0): Worker thread starting ...\r\n00001bf0.00001cac::2012\/05\/24-09:07:43.951 INFO\u00a0 [RES] SQL Server <SQL Server>: [sqsrvres] Worker Thread (A497A0): Entering SQLClusterSharedDataUpgradeWorker thread.\r\n00001bf0.00001cac::2012\/05\/24-09:07:43.951 INFO\u00a0 [RES] SQL Server <SQL Server>: [sqsrvres] Worker Thread (A497A0): SqlDataRoot = 'E:\\MSSQL10_50.MSSQLSERVER\\MSSQL',\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0CurrentPatchLevel = '10.51.2811.0',\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0SharedDataPatchLevel = '10.50.1600.1'\r\n00001bf0.00001cac::2012\/05\/24-09:07:43.951 INFO\u00a0 [RES] SQL Server <SQL Server>: [sqsrvres] Worker Thread (A497A0): FTDataPath = 'E:\\MSSQL10_50.MSSQLSERVER\\MSSQL\\FTData',\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0SQLGroup = 'S-1-5-80-3263513310-3392720605-1798839546-683002060-3227631582'\r\n00001bf0.00001cac::2012\/05\/24-09:07:43.951 INFO\u00a0 [RES] SQL Server <SQL Server>: [sqsrvres] Worker Thread (A497A0): Entering DoSQLDataRootApplyACL (E:\\MSSQL10_50.MSSQLSERVER\\MSSQL\\Data).\r\n00001bf0.00001cac::2012\/05\/24-09:07:43.951 WARN\u00a0 [RES] SQL Server <SQL Server>: [sqsrvres] Worker Thread (A497A0): DoSQLDataRootApplyACL : Failed to create directory tree at SQLDataRoot.\r\n00001bf0.00001cac::2012\/05\/24-09:07:43.951 INFO\u00a0 [RES] SQL Server <SQL Server>: [sqsrvres] Worker Thread (A497A0): Exiting DoSQLDataRootApplyACL (3).\r\n00001bf0.00001cac::2012\/05\/24-09:07:43.951 INFO\u00a0 [RES] SQL Server <SQL Server>: [sqsrvres] Worker Thread (A497A0): Exiting SQLClusterSharedDataUpgradeWorker thread (3).\r\n00001bf0.00001cac::2012\/05\/24-09:07:43.951 INFO\u00a0 [RES] SQL Server <SQL Server>: [sqsrvres] Worker Thread (A497A0): Worker thread exiting (retval = 3) ...\r\n00001bf0.00000c68::2012\/05\/24-09:07:43.951 INFO\u00a0 [RES] SQL Server <SQL Server>: [sqsrvres] Worker Thread (A497A0): Calling SQLClusterResourceWorker::WaitForCompletion (4294967295)\r\n00001bf0.00000c68::2012\/05\/24-09:07:43.951 ERR\u00a0\u00a0 [RES] SQL Server <SQL Server>: [sqsrvres] OnlineThread: SQL Cluster shared data upgrade failed\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0(status 0, Worker retval = 3)\r\n00001bf0.00000c68::2012\/05\/24-09:07:43.951 ERR\u00a0\u00a0 [RHS] Online for resource SQL Server failed.\r\n(...)<\/pre>\n
On voit clairement ici qu’il y a un probl\u00e8me de chemin:<\/p>\n
(...)\r\n[sqsrvres] Worker Thread (A497A0): SqlDataRoot =  'E:\\MSSQL10_50.MSSQLSERVER\\MSSQL',\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0  \u00a0CurrentPatchLevel = '10.51.2811.0',\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0  \u00a0SharedDataPatchLevel = '10.50.1600.1'\r\n(...)\r\n[sqsrvres] Worker Thread (A497A0):  DoSQLDataRootApplyACL : Failed to create directory tree at SQLDataRoot.\r\n(...)<\/pre>\n
En effet, pas de drive E: sur notre installation. Afin de respecter la norme du client, nous avions effectu\u00e9 un changement de lettre au niveau d’un des disques partag\u00e9s, passant de E:\\ \u00e0 M:\\, via la console d’administration du cluster. La modification n’avait pas \u00e9t\u00e9 pouss\u00e9e dans le registre. Il faut donc le faire, sur les 2 noeuds, manuellement, sous HKLM\\Softwares\\Microsoft\\Microsoft SQL Server\\MSSQL10_50.MSSQL\\Setup<\/em><\/p>\n
<\/p>\n
Une fois les chemins modifi\u00e9s, il faut remettre la ressource SQL Server en ligne et v\u00e9rifier dans l’ERRORLOG que l’upgrade a bien \u00e9t\u00e9 appliqu\u00e9:<\/p>\n
2012-05-24 11:17:44.05 Server\u00a0\u00a0\u00a0\u00a0\u00a0 Microsoft SQL Server 2008 R2 (SP1) - 10.50.2811.0 (X64)\r\nApr\u00a0 6 2012 01:59:29\r\nCopyright (c) Microsoft Corporation\r\nEnterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)\r\n(...)<\/pre>\n
Donc bottom-line, il faut penser \u00e0 v\u00e9rifier les chemins dans le registre pour les futurs upgrades lorsque l’on modifie une lettre de disque partag\u00e9 dans un cluster SQL Server.<\/p>\n
A+. David<\/p>\n\"twitter\"<\/a>\"linkedin\"<\/a>\"mail\"<\/a>","protected":false},"excerpt":{"rendered":"
Hello, Il existe d\u00e9j\u00e0 un post sur ce probl\u00e8me sp\u00e9cifique au patch de cluster\u00a0 SQL Server 2008 \/ 2008R2 ici, mais je suis tomb\u00e9 dessus ce matin et je me disais qu’il serait pas mal de poster un peu les… Continuer la lecture →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":7879,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[21,223],"class_list":["post-3621","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sqlserver","tag-cluster","tag-upgrade"],"yoast_head":"\n[sqsrvres] OnlineThread: SQL Cluster shared data upgrade failed - Capdata TECH BLOG<\/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:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"[sqsrvres] OnlineThread: SQL Cluster shared data upgrade failed - Capdata TECH BLOG\" \/>\n<meta property=\"og:description\" content=\"Hello, Il existe d\u00e9j\u00e0 un post sur ce probl\u00e8me sp\u00e9cifique au patch de cluster\u00a0 SQL Server 2008 \/ 2008R2 ici, mais je suis tomb\u00e9 dessus ce matin et je me disais qu’il serait pas mal de poster un peu les… Continuer la lecture →\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/\" \/>\n<meta property=\"og:site_name\" content=\"Capdata TECH BLOG\" \/>\n<meta property=\"article:published_time\" content=\"2012-05-24T10:07:35+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-12-19T08:30:34+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2012\/05\/sqlres.png\" \/>\n\t<meta property=\"og:image:width\" content=\"662\" \/>\n\t<meta property=\"og:image:height\" content=\"528\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"David Baffaleuf\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"David Baffaleuf\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/\"},\"author\":{\"name\":\"David Baffaleuf\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/person\/136297da9f61d6e4878abe0f48bc5fbf\"},\"headline\":\"[sqsrvres] OnlineThread: SQL Cluster shared data upgrade failed\",\"datePublished\":\"2012-05-24T10:07:35+00:00\",\"dateModified\":\"2022-12-19T08:30:34+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/\"},\"wordCount\":502,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/blog.capdata.fr\/#organization\"},\"keywords\":[\"cluster\",\"upgrade\"],\"articleSection\":[\"SQL Server\"],\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/\",\"url\":\"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/\",\"name\":\"[sqsrvres] OnlineThread: SQL Cluster shared data upgrade failed - Capdata TECH BLOG\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/#website\"},\"datePublished\":\"2012-05-24T10:07:35+00:00\",\"dateModified\":\"2022-12-19T08:30:34+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/blog.capdata.fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"[sqsrvres] OnlineThread: SQL Cluster shared data upgrade failed\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.capdata.fr\/#website\",\"url\":\"https:\/\/blog.capdata.fr\/\",\"name\":\"Capdata TECH BLOG\",\"description\":\"Le blog technique sur les bases de donn\u00e9es de CAP DATA Consulting\",\"publisher\":{\"@id\":\"https:\/\/blog.capdata.fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.capdata.fr\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/blog.capdata.fr\/#organization\",\"name\":\"Capdata TECH BLOG\",\"url\":\"https:\/\/blog.capdata.fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp\",\"contentUrl\":\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp\",\"width\":800,\"height\":254,\"caption\":\"Capdata TECH BLOG\"},\"image\":{\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.linkedin.com\/company\/cap-data-consulting\/mycompany\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/person\/136297da9f61d6e4878abe0f48bc5fbf\",\"name\":\"David Baffaleuf\",\"sameAs\":[\"http:\/\/www.capdata.fr\"],\"url\":\"https:\/\/blog.capdata.fr\/index.php\/author\/dbaffaleuf\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"[sqsrvres] OnlineThread: SQL Cluster shared data upgrade failed - Capdata TECH BLOG","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:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/","og_locale":"fr_FR","og_type":"article","og_title":"[sqsrvres] OnlineThread: SQL Cluster shared data upgrade failed - Capdata TECH BLOG","og_description":"Hello, Il existe d\u00e9j\u00e0 un post sur ce probl\u00e8me sp\u00e9cifique au patch de cluster\u00a0 SQL Server 2008 \/ 2008R2 ici, mais je suis tomb\u00e9 dessus ce matin et je me disais qu’il serait pas mal de poster un peu les… Continuer la lecture →","og_url":"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/","og_site_name":"Capdata TECH BLOG","article_published_time":"2012-05-24T10:07:35+00:00","article_modified_time":"2022-12-19T08:30:34+00:00","og_image":[{"width":662,"height":528,"url":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2012\/05\/sqlres.png","type":"image\/png"}],"author":"David Baffaleuf","twitter_card":"summary_large_image","twitter_misc":{"\u00c9crit par":"David Baffaleuf","Dur\u00e9e de lecture estim\u00e9e":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/#article","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/"},"author":{"name":"David Baffaleuf","@id":"https:\/\/blog.capdata.fr\/#\/schema\/person\/136297da9f61d6e4878abe0f48bc5fbf"},"headline":"[sqsrvres] OnlineThread: SQL Cluster shared data upgrade failed","datePublished":"2012-05-24T10:07:35+00:00","dateModified":"2022-12-19T08:30:34+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/"},"wordCount":502,"commentCount":0,"publisher":{"@id":"https:\/\/blog.capdata.fr\/#organization"},"keywords":["cluster","upgrade"],"articleSection":["SQL Server"],"inLanguage":"fr-FR","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/","url":"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/","name":"[sqsrvres] OnlineThread: SQL Cluster shared data upgrade failed - Capdata TECH BLOG","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/#website"},"datePublished":"2012-05-24T10:07:35+00:00","dateModified":"2022-12-19T08:30:34+00:00","breadcrumb":{"@id":"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.capdata.fr\/index.php\/sqsrvres-onlinethread-sql-cluster-shared-data-upgrade-failed\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/blog.capdata.fr\/"},{"@type":"ListItem","position":2,"name":"[sqsrvres] OnlineThread: SQL Cluster shared data upgrade failed"}]},{"@type":"WebSite","@id":"https:\/\/blog.capdata.fr\/#website","url":"https:\/\/blog.capdata.fr\/","name":"Capdata TECH BLOG","description":"Le blog technique sur les bases de donn\u00e9es de CAP DATA Consulting","publisher":{"@id":"https:\/\/blog.capdata.fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.capdata.fr\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/blog.capdata.fr\/#organization","name":"Capdata TECH BLOG","url":"https:\/\/blog.capdata.fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/","url":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp","contentUrl":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp","width":800,"height":254,"caption":"Capdata TECH BLOG"},"image":{"@id":"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.linkedin.com\/company\/cap-data-consulting\/mycompany\/"]},{"@type":"Person","@id":"https:\/\/blog.capdata.fr\/#\/schema\/person\/136297da9f61d6e4878abe0f48bc5fbf","name":"David Baffaleuf","sameAs":["http:\/\/www.capdata.fr"],"url":"https:\/\/blog.capdata.fr\/index.php\/author\/dbaffaleuf\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/3621","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/comments?post=3621"}],"version-history":[{"count":15,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/3621\/revisions"}],"predecessor-version":[{"id":9577,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/3621\/revisions\/9577"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media\/7879"}],"wp:attachment":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media?parent=3621"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/categories?post=3621"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/tags?post=3621"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}