{"id":7357,"date":"2019-03-21T18:00:02","date_gmt":"2019-03-21T17:00:02","guid":{"rendered":"http:\/\/blog.capdata.fr\/?p=7357"},"modified":"2022-11-21T17:09:19","modified_gmt":"2022-11-21T16:09:19","slug":"sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid","status":"publish","type":"post","link":"https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/","title":{"rendered":"SQL Server : resynchroniser un login avec le user d’une base apr\u00e8s une restauration gr\u00e2ce au SID"},"content":{"rendered":"\"twitter\"<\/a>\"linkedin\"<\/a>\"mail\"<\/a>

Voici un probl\u00e8me qui est bien connu des DBAs SQL Server en mati\u00e8re d’attributions de droits et mappings.<\/p>\n

Celui- ci est li\u00e9 \u00e0 la resynchronisation des logins et users bases de donn\u00e9es apr\u00e8s une restauration de bases.<\/p>\n

Au sein d’une instance SQL Server, chaque login a un SID qui est un identifiant repr\u00e9sentant une valeure hexad\u00e9ciamale unique au sein du moteur SQL Server.<\/p>\n

Il en va de m\u00eame pour un user d\u00e9clar\u00e9 sur une base de donn\u00e9es, ce SID est \u00e9galement unique et, il est g\u00e9n\u00e9ralement associ\u00e9 au login au moment du mapping du login au user base de donn\u00e9es attach\u00e9.
\nPour notre exemple, nous utiliserons une base de donn\u00e9es nomm\u00e9 “capdata_db” et un user nomm\u00e9 “manu” qui sera dbo sur cette base. Le login “manu” existe d\u00e9j\u00e0 au sein de l’instance.<\/p>\n

 <\/p>\n

USE [capdata_db]<\/span>
\nGO<\/span>
\nCREATE USER [manu] FOR LOGIN [manu]<\/span>
\nGO<\/span>
\nUSE [capdata_db]<\/span>
\nGO<\/span>
\nALTER USER [manu] WITH DEFAULT_SCHEMA=[dbo]<\/span>
\nGO<\/span><\/p>\n

 <\/p>\n

S’il l’on cherche les SID pour ce login et ce user bases de donn\u00e9es, cr\u00e9\u00e9 \u00e0 partir de ce login, nous voyons que les SID sont identiques :<\/p>\n

 <\/p>\n

use master<\/span>
\nselect name, sid from sys.syslogins where name =’manu’<\/span>
\ngo<\/span><\/p>\n

use capdata_db<\/span>
\nselect name, sid from sys.sysusers where name=’manu’<\/span>
\ngo<\/span><\/p>\n

 <\/p>\n

\"\"<\/p>\n

Le mapping pourra se voir dans les propri\u00e9t\u00e9s du login “manu” de l’instance.<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Cas d’une restauration<\/h3>\n

On imagine que l’on est sur un serveur de recette, et que, dans le cadre de tests d’un nouvel applicatif, nous souhaitons tester les donn\u00e9es fra\u00eeches de l’instance de production. Nous devrons alors, restaurer la base de donn\u00e9es “capdata_db” \u00e0 partir d’un serveur de production vers notre environnement de recette.<\/p>\n

Nous utiliserons le dernier backup de production que nous restaurerons sur la recette avec un PITR d\u00e9fini par les \u00e9quipes m\u00e9tier (restore database with norecovery, restore log with norecovery stopat….)<\/p>\n

Une fois cette base restaur\u00e9e, on regarde les users attach\u00e9s \u00e0 cette base. On voit bien qu’un user “manu” est pr\u00e9sent:<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Mais si l’on repasse les m\u00eames requ\u00eates qu’au d\u00e9but pour voir les SID du login et du user :<\/p>\n

 <\/p>\n

use master<\/span>
\nselect name, sid from sys.syslogins where name =’manu’<\/span>
\ngo<\/span><\/p>\n

use capdata_db<\/span>
\nselect name, sid from sys.sysusers where name=’manu’<\/span>
\ngo<\/span><\/p>\n

Cette fois ci, les SID sont diff\u00e9rents.<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

En regardant le mapping de notre login “manu” on voit qu’il a perdu son attachement \u00e0 la base “capdata_db” via le user “manu”, et surtout que ce mapping ne peut plus se faire :<\/p>\n

\"\"<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Le mapping entre le login “manu” et le user “manu” attribu\u00e9 \u00e0 la base n’est plus possible car un user de m\u00eame nom existe d\u00e9j\u00e0. Nous aurions pu passer par un nouveau user, par exemple “manu2” mais cela a pour cons\u00e9quence la perte des informations et des droits qui auraient \u00e9t\u00e9 configur\u00e9s en base.
\nS’il l’on \u00e9dite le script li\u00e9 \u00e0 ce processus, on voit en fait que le moteur SQL Server tente, par d\u00e9faut, de cr\u00e9er un nouveau user, et d’y attacher les droits ad\u00e9quat.<\/p>\n

 <\/p>\n

USE [capdata_db]<\/span>
\nGO<\/span>
\nCREATE USER [manu] FOR LOGIN [manu]<\/span>
\nGO<\/span>
\nUSE [capdata_db]<\/span>
\nGO<\/span>
\nALTER USER [manu] WITH DEFAULT_SCHEMA=[dbo]<\/span>
\nGO<\/span><\/p>\n

 <\/p>\n

Il ne sera donc pas possible de modifier un user via ALTER USER pour resynchroniser avec un login m\u00eame si celui ci est de m\u00eame nom<\/p>\n

 <\/p>\n

La cr\u00e9ation d’un nouveau login<\/h3>\n

L’\u00e9tape de resynchronisation login\/user va n\u00e9cessiter la recr\u00e9ation du login auparavant utilis\u00e9. Nous pourrons g\u00e9n\u00e9rer le DDL de cr\u00e9ation de ce login via l’option “Script login As \\ Create to” afin de reprendre les informations compl\u00e8te du login.<\/p>\n

DROP LOGIN [manu] <\/span>
\nGO<\/span><\/p>\n

CREATE LOGIN [manu] WITH PASSWORD=N’P0wsbkDGuBz8zmXSg\/Jrk\/fE5T4yzfBeTLpMIODi1t8=’, <\/span>
\nDEFAULT_DATABASE=[master], <\/span>
\nDEFAULT_LANGUAGE=[us_english], <\/span>
\nCHECK_EXPIRATION=OFF, <\/span>
\nCHECK_POLICY=ON<\/span>
\nGO<\/span><\/p>\n

 <\/p>\n

On ira modifier l’odre SQL ci dessus en y ajoutant l’option ‘SID=’ avec la valeure relev\u00e9 auparavant qui correspond \u00e0 celle du user d\u00e9fini en base.<\/p>\n

Dans notre cas, nous avions, apr\u00e8s restauration de la base<\/p>\n

\"\"<\/p>\n

 <\/p>\n

La requ\u00eate sera donc la suivante<\/p>\n

CREATE LOGIN [manu] WITH PASSWORD=N’P0wsbkDGuBz8zmXSg\/Jrk\/fE5T4yzfBeTLpMIODi1t8=’, <\/span>
\nSID=0xE19A6699AF282B47AF3CCE8E235447D7,<\/span>
\nDEFAULT_DATABASE=[master], <\/span>
\nDEFAULT_LANGUAGE=[us_english], <\/span>
\nCHECK_EXPIRATION=OFF, <\/span>
\nCHECK_POLICY=ON<\/span>
\nGO<\/span><\/p>\n

On se chargera de changer le mot de passer avec l’ancienne valeur si celui ci a \u00e9t\u00e9 laiss\u00e9 par d\u00e9faut par l’ordre CREATE LOGIN. Une fois le login recr\u00e9\u00e9, on verra que dans les propri\u00e9t\u00e9s de celui-ci, le mapping au user “manu” de la base “capdata_db” est effectu\u00e9 de fa\u00e7on automatique<\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Mais surtout, que son SID a chang\u00e9 et correspond \u00e0 celui du user en base<\/p>\n

 <\/p>\n

use master<\/span>
\nselect name, sid from sys.syslogins where name =’manu’<\/span>
\ngo<\/span><\/p>\n

use capdata_db<\/span>
\nselect name, sid from sys.sysusers where name=’manu’<\/span>
\ngo<\/span><\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

Les diff\u00e9rentes entr\u00e9es suivantes pr\u00e9sentes sur l’error_log devraient maintenant ne plus appara\u00eetre<\/p>\n

 <\/p>\n

2019-03-18 19:17:14.840 Logon Login failed for user ‘manu’. Reason: Failed to open the explicitly specified database ‘capdata_db’. [CLIENT: *******]<\/em><\/span>
\n2019-03-18 19:17:14.890 Logon Error: 18456, Severity: 14, State: 38.<\/em><\/span>
\n2019-03-18 19:17:14.890 Logon Login failed for user ‘manu’. Reason: Failed to open the explicitly specified database ‘capdata_db’. [CLIENT: *******]<\/em><\/span>
\n2019-03-18 19:17:14.890 Logon Error: 18456, Severity: 14, State: 38.<\/em><\/span><\/p>\n

 <\/p>\n

\ud83d\ude42<\/p>\n

N’h\u00e9sitez pas \u00e0 laisser un commentaire !<\/p>\n\"twitter\"<\/a>\"linkedin\"<\/a>\"mail\"<\/a>","protected":false},"excerpt":{"rendered":"

Voici un probl\u00e8me qui est bien connu des DBAs SQL Server en mati\u00e8re d’attributions de droits et mappings. Celui- ci est li\u00e9 \u00e0 la resynchronisation des logins et users bases de donn\u00e9es apr\u00e8s une restauration de bases. Au sein d’une… Continuer la lecture →<\/span><\/a><\/p>\n","protected":false},"author":32,"featured_media":7360,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-7357","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sqlserver"],"yoast_head":"\nSQL Server : resynchroniser un login avec le user d'une base apr\u00e8s une restauration gr\u00e2ce au SID - 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\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SQL Server : resynchroniser un login avec le user d'une base apr\u00e8s une restauration gr\u00e2ce au SID - Capdata TECH BLOG\" \/>\n<meta property=\"og:description\" content=\"Voici un probl\u00e8me qui est bien connu des DBAs SQL Server en mati\u00e8re d’attributions de droits et mappings. Celui- ci est li\u00e9 \u00e0 la resynchronisation des logins et users bases de donn\u00e9es apr\u00e8s une restauration de bases. Au sein d’une… Continuer la lecture →\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/\" \/>\n<meta property=\"og:site_name\" content=\"Capdata TECH BLOG\" \/>\n<meta property=\"article:published_time\" content=\"2019-03-21T17:00:02+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-11-21T16:09:19+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2019\/03\/sid_identiques.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"422\" \/>\n\t<meta property=\"og:image:height\" content=\"150\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Emmanuel RAMI\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"Emmanuel RAMI\" \/>\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\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/\"},\"author\":{\"name\":\"Emmanuel RAMI\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/person\/797b9b6698fa35f7ce3e9a70a8b102ae\"},\"headline\":\"SQL Server : resynchroniser un login avec le user d’une base apr\u00e8s une restauration gr\u00e2ce au SID\",\"datePublished\":\"2019-03-21T17:00:02+00:00\",\"dateModified\":\"2022-11-21T16:09:19+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/\"},\"wordCount\":953,\"commentCount\":2,\"publisher\":{\"@id\":\"https:\/\/blog.capdata.fr\/#organization\"},\"articleSection\":[\"SQL Server\"],\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/\",\"url\":\"https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/\",\"name\":\"SQL Server : resynchroniser un login avec le user d'une base apr\u00e8s une restauration gr\u00e2ce au SID - Capdata TECH BLOG\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/#website\"},\"datePublished\":\"2019-03-21T17:00:02+00:00\",\"dateModified\":\"2022-11-21T16:09:19+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/blog.capdata.fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SQL Server : resynchroniser un login avec le user d’une base apr\u00e8s une restauration gr\u00e2ce au SID\"}]},{\"@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\/797b9b6698fa35f7ce3e9a70a8b102ae\",\"name\":\"Emmanuel RAMI\",\"sameAs\":[\"https:\/\/blog.capdata.fr\"],\"url\":\"https:\/\/blog.capdata.fr\/index.php\/author\/erami\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"SQL Server : resynchroniser un login avec le user d'une base apr\u00e8s une restauration gr\u00e2ce au SID - 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\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/","og_locale":"fr_FR","og_type":"article","og_title":"SQL Server : resynchroniser un login avec le user d'une base apr\u00e8s une restauration gr\u00e2ce au SID - Capdata TECH BLOG","og_description":"Voici un probl\u00e8me qui est bien connu des DBAs SQL Server en mati\u00e8re d’attributions de droits et mappings. Celui- ci est li\u00e9 \u00e0 la resynchronisation des logins et users bases de donn\u00e9es apr\u00e8s une restauration de bases. Au sein d’une… Continuer la lecture →","og_url":"https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/","og_site_name":"Capdata TECH BLOG","article_published_time":"2019-03-21T17:00:02+00:00","article_modified_time":"2022-11-21T16:09:19+00:00","og_image":[{"width":422,"height":150,"url":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2019\/03\/sid_identiques.jpg","type":"image\/jpeg"}],"author":"Emmanuel RAMI","twitter_card":"summary_large_image","twitter_misc":{"\u00c9crit par":"Emmanuel RAMI","Dur\u00e9e de lecture estim\u00e9e":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/#article","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/"},"author":{"name":"Emmanuel RAMI","@id":"https:\/\/blog.capdata.fr\/#\/schema\/person\/797b9b6698fa35f7ce3e9a70a8b102ae"},"headline":"SQL Server : resynchroniser un login avec le user d’une base apr\u00e8s une restauration gr\u00e2ce au SID","datePublished":"2019-03-21T17:00:02+00:00","dateModified":"2022-11-21T16:09:19+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/"},"wordCount":953,"commentCount":2,"publisher":{"@id":"https:\/\/blog.capdata.fr\/#organization"},"articleSection":["SQL Server"],"inLanguage":"fr-FR","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/","url":"https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/","name":"SQL Server : resynchroniser un login avec le user d'une base apr\u00e8s une restauration gr\u00e2ce au SID - Capdata TECH BLOG","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/#website"},"datePublished":"2019-03-21T17:00:02+00:00","dateModified":"2022-11-21T16:09:19+00:00","breadcrumb":{"@id":"https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.capdata.fr\/index.php\/sql-server-resynchroniser-un-login-et-le-user-dune-base-apres-une-restauration-grace-au-sid\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/blog.capdata.fr\/"},{"@type":"ListItem","position":2,"name":"SQL Server : resynchroniser un login avec le user d’une base apr\u00e8s une restauration gr\u00e2ce au SID"}]},{"@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\/797b9b6698fa35f7ce3e9a70a8b102ae","name":"Emmanuel RAMI","sameAs":["https:\/\/blog.capdata.fr"],"url":"https:\/\/blog.capdata.fr\/index.php\/author\/erami\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/7357","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\/32"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/comments?post=7357"}],"version-history":[{"count":10,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/7357\/revisions"}],"predecessor-version":[{"id":9537,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/7357\/revisions\/9537"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media\/7360"}],"wp:attachment":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media?parent=7357"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/categories?post=7357"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/tags?post=7357"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}