{"id":3500,"date":"2012-04-16T10:37:10","date_gmt":"2012-04-16T09:37:10","guid":{"rendered":"http:\/\/blog.capdata.fr\/?p=3500"},"modified":"2019-09-13T14:20:12","modified_gmt":"2019-09-13T13:20:12","slug":"production-sql-server-banalisation-des-instances","status":"publish","type":"post","link":"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/","title":{"rendered":"Production SQL Server : banalisation des instances"},"content":{"rendered":"<a class=\"synved-social-button synved-social-button-share synved-social-size-24 synved-social-resolution-single synved-social-provider-twitter nolightbox\" data-provider=\"twitter\" target=\"_blank\" rel=\"nofollow\" title=\"Share on Twitter\" href=\"https:\/\/twitter.com\/intent\/tweet?url=https%3A%2F%2Fblog.capdata.fr%2Findex.php%2Fwp-json%2Fwp%2Fv2%2Fposts%2F3500&#038;text=Article%20sur%20le%20blog%20de%20la%20Capdata%20Tech%20Team%20%3A%20\" style=\"font-size: 0px;width:24px;height:24px;margin:0;margin-bottom:5px;margin-right:5px\"><img loading=\"lazy\" decoding=\"async\" alt=\"twitter\" title=\"Share on Twitter\" class=\"synved-share-image synved-social-image synved-social-image-share\" width=\"24\" height=\"24\" style=\"display: inline;width:24px;height:24px;margin: 0;padding: 0;border: none;box-shadow: none\" src=\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/twitter.png\" \/><\/a><a class=\"synved-social-button synved-social-button-share synved-social-size-24 synved-social-resolution-single synved-social-provider-linkedin nolightbox\" data-provider=\"linkedin\" target=\"_blank\" rel=\"nofollow\" title=\"Share on Linkedin\" href=\"https:\/\/www.linkedin.com\/shareArticle?mini=true&#038;url=https%3A%2F%2Fblog.capdata.fr%2Findex.php%2Fwp-json%2Fwp%2Fv2%2Fposts%2F3500&#038;title=Production%20SQL%20Server%20%3A%20banalisation%20des%20instances\" style=\"font-size: 0px;width:24px;height:24px;margin:0;margin-bottom:5px;margin-right:5px\"><img loading=\"lazy\" decoding=\"async\" alt=\"linkedin\" title=\"Share on Linkedin\" class=\"synved-share-image synved-social-image synved-social-image-share\" width=\"24\" height=\"24\" style=\"display: inline;width:24px;height:24px;margin: 0;padding: 0;border: none;box-shadow: none\" src=\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/linkedin.png\" \/><\/a><a class=\"synved-social-button synved-social-button-share synved-social-size-24 synved-social-resolution-single synved-social-provider-mail nolightbox\" data-provider=\"mail\" rel=\"nofollow\" title=\"Share by email\" href=\"mailto:?subject=Production%20SQL%20Server%20%3A%20banalisation%20des%20instances&#038;body=Article%20sur%20le%20blog%20de%20la%20Capdata%20Tech%20Team%20%3A%20:%20https%3A%2F%2Fblog.capdata.fr%2Findex.php%2Fwp-json%2Fwp%2Fv2%2Fposts%2F3500\" style=\"font-size: 0px;width:24px;height:24px;margin:0;margin-bottom:5px\"><img loading=\"lazy\" decoding=\"async\" alt=\"mail\" title=\"Share by email\" class=\"synved-share-image synved-social-image synved-social-image-share\" width=\"24\" height=\"24\" style=\"display: inline;width:24px;height:24px;margin: 0;padding: 0;border: none;box-shadow: none\" src=\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/mail.png\" \/><\/a><p>Septi\u00e8me article de la s\u00e9rie <a href=\"http:\/\/blog.capdata.fr\/index.php\/une-approche-pragmatique-de-la-production-sql-server\">Une approche pragmatique de la production SQL Server<\/a>, c\u2019est le couple normalisation\/banalisation qui est abord\u00e9 ici.<\/p>\n<p><em>(On me glisse \u00e0 l\u2019oreillette que le terme \u00ab\u00a0banalisation\u00a0\u00bb n\u2019est jamais employ\u00e9 dans le domaine de la base de donn\u00e9es, mais puisque je le trouve assez bien adapt\u00e9 au concept que j\u2019aborde ici, je l\u2019utiliserai quand m\u00eame\u00a0!)<\/em><\/p>\n<p>Par instance normalis\u00e9e, j\u2019entends instance install\u00e9e selon un ensemble de r\u00e8gles d\u00e9finissant\u00a0:<\/p>\n<ul>\n<li>L\u2019\u00e9dition et la version de SQL Server,<\/li>\n<li>l\u2019emplacement des diff\u00e9rents fichiers,<\/li>\n<li>le nommage de l\u2019instance,<\/li>\n<li>le port TCP de l\u2019instance,<\/li>\n<li>Le mot de passe du login sa et la liste des logins disposant de forts privil\u00e8ges,<\/li>\n<li>La Collation de l\u2019instance<\/li>\n<li>Le nom et le contenu de la base contenant les scripts d\u2019exploitation,<\/li>\n<li>Le compte de service qui lance SQL Server et SQL Agent, et les privil\u00e8ges de ce compte sur la machine<\/li>\n<\/ul>\n<p>Par instance banalis\u00e9e, j\u2019entends instance configur\u00e9e avec des valeurs fixes pour certains param\u00e8tres\u00a0:<\/p>\n<ul>\n<li>M\u00e9moire allou\u00e9e<\/li>\n<li>Masque CPU<\/li>\n<li>Param\u00e8tres de configuration tels que xp_cmdshell, backup compression default, clr enabled, cross db ownership, cost threshold for parallelism, max degree of parallelism<\/li>\n<\/ul>\n<p>L\u2019id\u00e9e est donc de mettre \u00e0 disposition une instance qui aura une configuration correspondant \u00e0 peu pr\u00e8s \u00e0 tous les types d\u2019utilisation.<\/p>\n<p><strong>Pourquoi banaliser\u00a0?<\/strong><\/p>\n<ul>\n<li>D\u00e9ployer une instance banalis\u00e9e est tr\u00e8s simple. Il suffit de lancer un script de post installation pour fixer les valeurs des param\u00e8tres, qui peut \u00eatre facilement inclus dans le processus de d\u00e9ploiement.<\/li>\n<li>Mettre en place la supervision d\u2019une instance banalis\u00e9e est aussi tr\u00e8s simple, puisque les seuils de consommation de ressources sont les m\u00eames.<\/li>\n<li>Puisque les instances sont les m\u00eames, le DBA est toujours en environnement connu pour tout ce qui est t\u00e2ches courantes d\u2019exploitation et gestion d\u2019incidents.<\/li>\n<\/ul>\n<p><strong>Faut-il tout banaliser\u00a0?<\/strong><\/p>\n<p>Bien s\u00fbr que non\u00a0!<\/p>\n<p>Une instance banalis\u00e9e, par d\u00e9finition, n\u2019est pas optimis\u00e9e pour l\u2019usage qui en est fait. Mais en nous basant sur la r\u00e8gle dite des 80\/20, il semble r\u00e9aliste de banaliser 80% des instances, ce qui permettra de concentrer la charge de travail du DBA sur les 20% des instances restantes (a priori les 20% les plus critiques).<\/p>\n<p><strong>Et concr\u00eatement\u00a0?<\/strong><\/p>\n<p>Une fois vos r\u00e8gles de normalisation d\u00e9finies, utilisez l\u2019option \u00a0\u00ab\u00a0<a href=\"http:\/\/msdn.microsoft.com\/en-us\/library\/dd239405.aspx\">configuration file <\/a>\u00bb de SQL Server Installation Center pour faciliter l\u2019installation\u00a0:<\/p>\n<ol>\n<li>Lancez une installation classique en vous arr\u00eatant \u00e0 la derni\u00e8re \u00e9tape. Rien ne sera install\u00e9, mais un fichier de configuration sera g\u00e9n\u00e9r\u00e9.<\/li>\n<li>Editez ce fichier en rempla\u00e7ant certaines valeurs par des variables (nom d\u2019instance, chemin des fichiers de donn\u00e9es et de journaux, compte de service, \u2026), afin d\u2019en faire un mod\u00e8le.<\/li>\n<p><em> Exemple de fichier &#8220;configurationfile.modele&#8221; issu d&#8217;une installation de SQL Server 2012:<\/em><br \/>\n<code>[OPTIONS]<br \/>\nACTION=\"Install\"<br \/>\nENU=\"True\"<br \/>\nUIMODE=\"Normal\"<br \/>\nQUIET=\"False\"<br \/>\nQUIETSIMPLE=\"False\"<br \/>\nUpdateEnabled=\"False\"<br \/>\nFEATURES=SQLENGINE<br \/>\nUpdateSource=\"MU\"<br \/>\nHELP=\"False\"<br \/>\nINDICATEPROGRESS=\"False\"<br \/>\nINSTALLSHAREDDIR=\"C:\\Program Files\\Microsoft SQL Server\"<br \/>\nINSTANCENAME=\"%INSTANCE%\"<br \/>\nINSTANCEID=\"%INSTANCE%\"<br \/>\nSQMREPORTING=\"False\"<br \/>\nERRORREPORTING=\"False\"<br \/>\nINSTANCEDIR=\"C:\\Program Files\\Microsoft SQL Server\"<br \/>\nAGTSVCACCOUNT=\"%COMPTESERVICE%\"<br \/>\nAGTSVCPASSWORD=\"%MDPCOMPTESERVICE%\"<br \/>\nAGTSVCSTARTUPTYPE=\"Automatic\"<br \/>\nCOMMFABRICPORT=\"0\"<br \/>\nCOMMFABRICNETWORKLEVEL=\"0\"<br \/>\nCOMMFABRICENCRYPTION=\"0\"<br \/>\nMATRIXCMBRICKCOMMPORT=\"0\"<br \/>\nSQLSVCSTARTUPTYPE=\"Automatic\"<br \/>\nFILESTREAMLEVEL=\"0\"<br \/>\nENABLERANU=\"False\"<br \/>\nSQLCOLLATION=\"French_CI_AS\"<br \/>\nSQLSVCACCOUNT=\"%COMPTESERVICE%\"<br \/>\nSQLSVCPASSWORD=\"%MDPCOMPTESERVICE%\"<br \/>\nSQLSYSADMINACCOUNTS=\"%GROUPESYSADMIN%\"<br \/>\nSECURITYMODE=\"SQL\"<br \/>\nSQLBACKUPDIR=\"D:\\BACKUP\\%INSTANCE%\"<br \/>\nSQLUSERDBDIR=\"D:\\DATA\\%INSTANCE%\"<br \/>\nSQLUSERDBLOGDIR=\"D:\\TLOG\\%INSTANCE%\"<br \/>\nSQLTEMPDBDIR=\"D:\\DATA\\%INSTANCE%\"<br \/>\nSQLTEMPDBLOGDIR=\"D:\\TLOG\\%INSTANCE%\"<br \/>\nADDCURRENTUSERASSQLADMIN=\"False\"<br \/>\nTCPENABLED=\"1\"<br \/>\nNPENABLED=\"0\"<br \/>\nBROWSERSVCSTARTUPTYPE=\"Automatic\"<\/code><\/p>\n<li>Cr\u00e9ez un fichier de commandes qui valorise les variables, g\u00e9n\u00e8re \u00e0 la vol\u00e9e un fichier de configuration puis appelle le setup.exe de SQL Server en utilisant le fichier de configuration g\u00e9n\u00e9r\u00e9.<\/li>\n<p><em>Exemple de script d&#8217;installation &#8220;install_sql.cmd&#8221;<\/em><br \/>\n<code>@echo off<br \/>\ndel configurationfile.ini<br \/>\necho Nom de l'instance \u00e0 installer:<br \/>\nset \/p INSTANCE=<br \/>\necho Compte de Service windows:<br \/>\nset \/p COMPTESERVICE=<br \/>\necho Mot de passe du compte de Service windows<br \/>\nset \/p MDPCOMPTESERVICE=<br \/>\necho Groupe(s) Sysadmin:<br \/>\nset \/p GROUPESYSADMIN=<\/code><\/p>\n<p><code>for \/f \"delims=\" %%i in ('type configurationfile.modele') do (<br \/>\ncall echo %%i&gt;&gt;configurationfile.ini<br \/>\n)<\/code><\/p>\n<p><code> <\/code><\/p>\n<p><code>I:\\setup.exe \/configurationfile=configurationfile.ini<br \/>\n<\/code><\/p>\n<li>Cr\u00e9ez un script sql contenant toutes les modifications de configuration correspondant \u00e0 votre banalisation, et lancez le apr\u00e8s chaque installation (le lancement peut bien entendu \u00eatre inclus dans le script d&#8217;installation&#8230;)<\/li>\n<\/ol>\n<p><em>Exemple de script de banalisation &#8220;banalisation.sql&#8221;<\/em><\/p>\n<pre name=\"code\" class=\"sql\">\r\n\/***************************************************************************\r\n   ^\r\n  \/ \\\r\n \/ ! \\\tATTENTION\r\n\/_____\\\r\n\r\nLes modifications propos\u00e9es dans ce script auront un impact\r\nsur le fonctionnement de votre instance SQL Server (performances, s\u00e9curit\u00e9).\r\nIl est donc imp\u00e9ratif de prendre connaissance des modifications propos\u00e9es et\r\nde ne les mettre en place que lorsque les impacts sont ma\u00eetris\u00e9s.\r\n\r\nCap Data consulting ne saurait \u00eatre tenue responsable des cons\u00e9quences du\r\nlancement de ce script sur un syst\u00e8me.\r\n**************************************************************************\/\r\nset nocount on\r\ndeclare @commande varchar(200), @cpus int, @memoire_physique int, @MAX_DOP int, @MEMOIRE_INSTANCE int, @chemin_fichiers_tempdb nvarchar(520), @compteur int\r\nselect @cpus=cpu_count, @memoire_physique=physical_memory_in_bytes\/1048576 from sys.dm_os_sys_info\r\n\r\nSELECT\t @MAX_DOP=4\t\t\t\t--Degr\u00e9 max de parall\u00e9lisme\r\n\t\t,@MEMOIRE_INSTANCE=512 --M\u00e9moire \u00e0 allouer \u00e0 l'instance\r\n\r\nIF (@MAX_DOP&gt;@cpus)select @MAX_DOP=@cpus\r\nIF (@MEMOIRE_INSTANCE &gt; @memoire_physique - 512)select @MEMOIRE_INSTANCE = @memoire_physique - 512 \r\n\r\n-- Param\u00e8tres de l'instance\r\nEXEC sp_configure 'show advanced options', 1\r\nreconfigure\r\ncreate table #parametres(nom nvarchar(35), valeur int)\r\ninsert into #parametres values\t('max degree of parallelism', @MAX_DOP),\r\n\t\t\t\t\t\t\t\t('min server memory (MB)', @MEMOIRE_INSTANCE),\r\n\t\t\t\t\t\t\t\t('max server memory (MB)', @MEMOIRE_INSTANCE),\r\n\t\t\t\t\t\t\t\t('remote admin connections',1 ),\r\n\t\t\t\t\t\t\t\t('xp_cmdshell', 1),\r\n\t\t\t\t\t\t\t\t('backup compression default', 1)\r\n\r\nDECLARE CURSEUR_PARAMETRES INSENSITIVE CURSOR FOR\r\nselect 'sp_configure '''+nom+''', '+cast(valeur as varchar(10)) from #parametres P\r\ninner join sys.configurations C ON P.nom=C.name\r\nWHERE P.valeur !=cast(C.value as int)\r\nand P.valeur between cast(C.minimum as int) and cast(C.maximum as int)\r\norder by nom \r\n\r\nOPEN CURSEUR_PARAMETRES\r\nFETCH NEXT FROM CURSEUR_PARAMETRES  into @commande\r\nWHILE(@@FETCH_STATUS=0)\r\nBEGIN\r\n\tPRINT @commande\r\n\tEXEC(@commande)\r\n\tFETCH NEXT FROM CURSEUR_PARAMETRES  into @commande\r\nEND\r\nCLOSE CURSEUR_PARAMETRES\r\nDEALLOCATE CURSEUR_PARAMETRES\r\ndrop table #parametres\r\n\r\n--Modification de TempDB\r\nalter database tempdb modify file(name='tempdev', SIZE=128 MB, MAXSIZE = UNLIMITED, FILEGROWTH= 128 MB)\r\nselect @chemin_fichiers_tempdb=replace(physical_name,'tempdb.mdf','') from tempdb.sys.database_files where file_id=1\r\nselect @compteur=count(1)+1 FROM tempdb.sys.database_files where type_desc='ROWS'\r\nWHILE(@compteur &lt; =@cpus)\r\nBEGIN\r\n\tset @commande='ALTER DATABASE tempdb ADD FILE (NAME=''tempdev_'+cast(@compteur as varchar(3))+''', FILENAME='''+@chemin_fichiers_tempdb+'tempdb_'+cast(@compteur as varchar(3))+'.ndf'', SIZE=128 MB, MAXSIZE=UNLIMITED, FILEGROWTH=128 MB)'\r\n\tPRINT @commande\r\n\tselect @compteur = @compteur + 1\r\nEND\r\n\r\n--Modification de Model\r\nalter database model modify file(name='modeldev', MAXSIZE = UNLIMITED, FILEGROWTH= 128 MB)\r\nalter database model modify file(name='modellog', MAXSIZE = UNLIMITED, FILEGROWTH= 128 MB)\r\nalter database model set recovery SIMPLE<\/pre>\n<p>Enfin, sachez que gr\u00e2ce au m\u00e9canisme de &#8220;<a href=\"http:\/\/technet.microsoft.com\/en-us\/library\/bb510667.aspx\">Policy Management<\/a>&#8221; de SQL Server, vous disposez d&#8217;un moyen simple de v\u00e9rifier r\u00e9guli\u00e8rement que la configuration des instances est toujours celle que vous avez d\u00e9fini \u00e0 l&#8217;installation.<\/p>\n<a class=\"synved-social-button synved-social-button-share synved-social-size-24 synved-social-resolution-single synved-social-provider-twitter nolightbox\" data-provider=\"twitter\" target=\"_blank\" rel=\"nofollow\" title=\"Share on Twitter\" href=\"https:\/\/twitter.com\/intent\/tweet?url=https%3A%2F%2Fblog.capdata.fr%2Findex.php%2Fwp-json%2Fwp%2Fv2%2Fposts%2F3500&#038;text=Article%20sur%20le%20blog%20de%20la%20Capdata%20Tech%20Team%20%3A%20\" style=\"font-size: 0px;width:24px;height:24px;margin:0;margin-bottom:5px;margin-right:5px\"><img loading=\"lazy\" decoding=\"async\" alt=\"twitter\" title=\"Share on Twitter\" class=\"synved-share-image synved-social-image synved-social-image-share\" width=\"24\" height=\"24\" style=\"display: inline;width:24px;height:24px;margin: 0;padding: 0;border: none;box-shadow: none\" src=\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/twitter.png\" \/><\/a><a class=\"synved-social-button synved-social-button-share synved-social-size-24 synved-social-resolution-single synved-social-provider-linkedin nolightbox\" data-provider=\"linkedin\" target=\"_blank\" rel=\"nofollow\" title=\"Share on Linkedin\" href=\"https:\/\/www.linkedin.com\/shareArticle?mini=true&#038;url=https%3A%2F%2Fblog.capdata.fr%2Findex.php%2Fwp-json%2Fwp%2Fv2%2Fposts%2F3500&#038;title=Production%20SQL%20Server%20%3A%20banalisation%20des%20instances\" style=\"font-size: 0px;width:24px;height:24px;margin:0;margin-bottom:5px;margin-right:5px\"><img loading=\"lazy\" decoding=\"async\" alt=\"linkedin\" title=\"Share on Linkedin\" class=\"synved-share-image synved-social-image synved-social-image-share\" width=\"24\" height=\"24\" style=\"display: inline;width:24px;height:24px;margin: 0;padding: 0;border: none;box-shadow: none\" src=\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/linkedin.png\" \/><\/a><a class=\"synved-social-button synved-social-button-share synved-social-size-24 synved-social-resolution-single synved-social-provider-mail nolightbox\" data-provider=\"mail\" rel=\"nofollow\" title=\"Share by email\" href=\"mailto:?subject=Production%20SQL%20Server%20%3A%20banalisation%20des%20instances&#038;body=Article%20sur%20le%20blog%20de%20la%20Capdata%20Tech%20Team%20%3A%20:%20https%3A%2F%2Fblog.capdata.fr%2Findex.php%2Fwp-json%2Fwp%2Fv2%2Fposts%2F3500\" style=\"font-size: 0px;width:24px;height:24px;margin:0;margin-bottom:5px\"><img loading=\"lazy\" decoding=\"async\" alt=\"mail\" title=\"Share by email\" class=\"synved-share-image synved-social-image synved-social-image-share\" width=\"24\" height=\"24\" style=\"display: inline;width:24px;height:24px;margin: 0;padding: 0;border: none;box-shadow: none\" src=\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/mail.png\" \/><\/a>","protected":false},"excerpt":{"rendered":"<p>Septi\u00e8me article de la s\u00e9rie Une approche pragmatique de la production SQL Server, c\u2019est le couple normalisation\/banalisation qui est abord\u00e9 ici. (On me glisse \u00e0 l\u2019oreillette que le terme \u00ab\u00a0banalisation\u00a0\u00bb n\u2019est jamais employ\u00e9 dans le domaine de la base de&hellip; <a href=\"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/\" class=\"more-link\">Continuer la lecture <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":14,"featured_media":7884,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[206,33,212],"class_list":["post-3500","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sqlserver","tag-howto","tag-installation","tag-production"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v20.8 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Production SQL Server : banalisation des instances - 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\/production-sql-server-banalisation-des-instances\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Production SQL Server : banalisation des instances - Capdata TECH BLOG\" \/>\n<meta property=\"og:description\" content=\"Septi\u00e8me article de la s\u00e9rie Une approche pragmatique de la production SQL Server, c\u2019est le couple normalisation\/banalisation qui est abord\u00e9 ici. (On me glisse \u00e0 l\u2019oreillette que le terme \u00ab\u00a0banalisation\u00a0\u00bb n\u2019est jamais employ\u00e9 dans le domaine de la base de&hellip; Continuer la lecture &rarr;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/\" \/>\n<meta property=\"og:site_name\" content=\"Capdata TECH BLOG\" \/>\n<meta property=\"article:published_time\" content=\"2012-04-16T09:37:10+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2019-09-13T13:20:12+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2012\/04\/std.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"500\" \/>\n\t<meta property=\"og:image:height\" content=\"401\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Benjamin VESAN\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"Benjamin VESAN\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 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\/production-sql-server-banalisation-des-instances\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/\"},\"author\":{\"name\":\"Benjamin VESAN\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/person\/ae56d1d3d5680d95ccc2c927e44bdc3e\"},\"headline\":\"Production SQL Server : banalisation des instances\",\"datePublished\":\"2012-04-16T09:37:10+00:00\",\"dateModified\":\"2019-09-13T13:20:12+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/\"},\"wordCount\":618,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/blog.capdata.fr\/#organization\"},\"keywords\":[\"howto\",\"installation\",\"Production\"],\"articleSection\":[\"SQL Server\"],\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/\",\"url\":\"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/\",\"name\":\"Production SQL Server : banalisation des instances - Capdata TECH BLOG\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/#website\"},\"datePublished\":\"2012-04-16T09:37:10+00:00\",\"dateModified\":\"2019-09-13T13:20:12+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/blog.capdata.fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Production SQL Server : banalisation des instances\"}]},{\"@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\/ae56d1d3d5680d95ccc2c927e44bdc3e\",\"name\":\"Benjamin VESAN\",\"url\":\"https:\/\/blog.capdata.fr\/index.php\/author\/bvesan\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Production SQL Server : banalisation des instances - 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\/production-sql-server-banalisation-des-instances\/","og_locale":"fr_FR","og_type":"article","og_title":"Production SQL Server : banalisation des instances - Capdata TECH BLOG","og_description":"Septi\u00e8me article de la s\u00e9rie Une approche pragmatique de la production SQL Server, c\u2019est le couple normalisation\/banalisation qui est abord\u00e9 ici. (On me glisse \u00e0 l\u2019oreillette que le terme \u00ab\u00a0banalisation\u00a0\u00bb n\u2019est jamais employ\u00e9 dans le domaine de la base de&hellip; Continuer la lecture &rarr;","og_url":"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/","og_site_name":"Capdata TECH BLOG","article_published_time":"2012-04-16T09:37:10+00:00","article_modified_time":"2019-09-13T13:20:12+00:00","og_image":[{"width":500,"height":401,"url":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2012\/04\/std.jpg","type":"image\/jpeg"}],"author":"Benjamin VESAN","twitter_card":"summary_large_image","twitter_misc":{"\u00c9crit par":"Benjamin VESAN","Dur\u00e9e de lecture estim\u00e9e":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/#article","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/"},"author":{"name":"Benjamin VESAN","@id":"https:\/\/blog.capdata.fr\/#\/schema\/person\/ae56d1d3d5680d95ccc2c927e44bdc3e"},"headline":"Production SQL Server : banalisation des instances","datePublished":"2012-04-16T09:37:10+00:00","dateModified":"2019-09-13T13:20:12+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/"},"wordCount":618,"commentCount":0,"publisher":{"@id":"https:\/\/blog.capdata.fr\/#organization"},"keywords":["howto","installation","Production"],"articleSection":["SQL Server"],"inLanguage":"fr-FR","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/","url":"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/","name":"Production SQL Server : banalisation des instances - Capdata TECH BLOG","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/#website"},"datePublished":"2012-04-16T09:37:10+00:00","dateModified":"2019-09-13T13:20:12+00:00","breadcrumb":{"@id":"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.capdata.fr\/index.php\/production-sql-server-banalisation-des-instances\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/blog.capdata.fr\/"},{"@type":"ListItem","position":2,"name":"Production SQL Server : banalisation des instances"}]},{"@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\/ae56d1d3d5680d95ccc2c927e44bdc3e","name":"Benjamin VESAN","url":"https:\/\/blog.capdata.fr\/index.php\/author\/bvesan\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/3500","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\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/comments?post=3500"}],"version-history":[{"count":33,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/3500\/revisions"}],"predecessor-version":[{"id":3541,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/3500\/revisions\/3541"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media\/7884"}],"wp:attachment":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media?parent=3500"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/categories?post=3500"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/tags?post=3500"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}