{"id":12767,"date":"2025-12-17T14:20:09","date_gmt":"2025-12-17T13:20:09","guid":{"rendered":"https:\/\/sdna.lu\/?p=12767"},"modified":"2025-12-17T17:14:06","modified_gmt":"2025-12-17T16:14:06","slug":"12767","status":"publish","type":"post","link":"https:\/\/sdna.lu\/?p=12767","title":{"rendered":"Backup  MS  Access"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>\u00c9volution de notre politique de sauvegarde des bases de donn\u00e9es<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Contexte technique&nbsp;:<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Depuis plusieurs ann\u00e9es, nous utilisons Microsoft Database Engine (Access \/ Jet \/ ACE) pour cr\u00e9er les sauvegardes de bases de donn\u00e9es DeMaSy.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Cependant, nous rencontrons de plus en plus de probl\u00e8mes de compatibilit\u00e9 entre Microsoft Database Engine et les mises \u00e0 jour r\u00e9guli\u00e8res de Windows (Windows 10 et Windows 11).<br>Ces mises \u00e0 jour provoquent fr\u00e9quemment <\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Des erreurs d\u2019ex\u00e9cution impr\u00e9visibles,<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Des probl\u00e8mes de pilotes ODBC\/OLEDB,<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Des conflits de versions (32 bits \/ 64 bits),<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Des dysfonctionnements lors des op\u00e9rations de backup ou de compression,<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Une instabilit\u00e9 g\u00e9n\u00e9rale des processus automatis\u00e9s.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Malgr\u00e9 nos tentatives de contournement, ces probl\u00e9matiques sont hors de notre contr\u00f4le, car elles d\u00e9pendent directement des choix techniques et des mises \u00e0 jour impos\u00e9es par Microsoft.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Fin du support des sauvegardes via MS Access<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dans ce contexte, et afin de garantir la fiabilit\u00e9, la s\u00e9curit\u00e9 et la p\u00e9rennit\u00e9 de notre solution, nous avons d\u00e9cid\u00e9 de :<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong><mark style=\"background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-red-color\">Mettre fin progressivement au support des sauvegardes de bases de donn\u00e9es bas\u00e9es sur MS Access.<\/mark><\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Cette \u00e9volution sera effective dans les mois \u00e0 venir et dans la version 12.<br>La m\u00e9thode de backup MS Access ne sera donc plus maintenue ni support\u00e9e apr\u00e8s cette p\u00e9riode de transition. Cependant, il sera toujours possible de restaurer de vieilles sauvegardes MS Access cr\u00e9es dans des versions pr\u00e9c\u00e9dentes \u00e0 la version 12. (Sous conditions que le Acess Database Engine soit install\u00e9 sur votre environnement et ne pose pas de probl\u00e8mes avec les diff\u00e9rentes mises a jour de windows)<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Nouvelle approche recommand\u00e9e<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sauvegarde directe via SQL Server (m\u00e9thode privil\u00e9gi\u00e9e)<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Il sera d\u00e9sormais n\u00e9cessaire de nous fournir :<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>le mot de passe du compte sa<br>OU<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>un compte SQL Server disposant de droits \u00e9quivalents (backup, restore, acc\u00e8s aux bases concern\u00e9es).<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Cela nous permettra :<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>D\u2019ex\u00e9cuter des sauvegardes natives SQL Server,<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>D\u2019assurer une meilleure fiabilit\u00e9,<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>De supprimer toute d\u00e9pendance \u00e0 Microsoft Database Engine et \u00e0 Access.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Cette m\u00e9thode est la plus robuste et la plus recommand\u00e9e.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Alternative : sauvegarde au format XML<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pour les clients ne souhaitant pas fournir d\u2019acc\u00e8s administrateur SQL Server, une m\u00e9thode alternative sera propos\u00e9e :<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Export des donn\u00e9es sous forme de sauvegardes XML,<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Solution ind\u00e9pendante de MS Access,<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Compatible avec nos outils et processus futurs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>\u00c0 noter :<\/strong><br>Les sauvegardes XML peuvent avoir certaines limitations (taille, temps de traitement, restauration partielle selon les cas) par rapport \u00e0 une sauvegarde SQL Server compl\u00e8te.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">P\u00e9riode de transition<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Une p\u00e9riode de transition sera mise en place afin de permettre \u00e0 chaque client de :<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Choisir la m\u00e9thode de sauvegarde la plus adapt\u00e9e,<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Mettre \u00e0 jour ses acc\u00e8s SQL Server si n\u00e9cessaire,<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Anticiper la fin du support Access sans interruption de service.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Nos \u00e9quipes restent bien entendu disponibles pour accompagner cette transition et r\u00e9pondre \u00e0 toute question technique.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Conclusion<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Cette d\u00e9cision vise avant tout \u00e0 :<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Am\u00e9liorer la stabilit\u00e9 de nos solutions,<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Garantir la s\u00e9curit\u00e9 des donn\u00e9es,<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>R\u00e9duire les risques li\u00e9s aux mises \u00e0 jour Windows,<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>S\u2019aligner sur les bonnes pratiques actuelles en mati\u00e8re de gestion de bases de donn\u00e9es.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>\u00c9volution de notre politique de sauvegarde des bases de donn\u00e9es Contexte technique&nbsp;: Depuis plusieurs ann\u00e9es, nous utilisons Microsoft Database Engine (Access \/ Jet \/ ACE) pour cr\u00e9er les sauvegardes de bases de donn\u00e9es DeMaSy. Cependant, nous rencontrons de plus en plus de probl\u00e8mes de compatibilit\u00e9 entre Microsoft Database Engine et les mises \u00e0 jour r\u00e9guli\u00e8res [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-12767","post","type-post","status-publish","format-standard","hentry","category-non-classe"],"_links":{"self":[{"href":"https:\/\/sdna.lu\/index.php?rest_route=\/wp\/v2\/posts\/12767","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sdna.lu\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sdna.lu\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sdna.lu\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sdna.lu\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=12767"}],"version-history":[{"count":8,"href":"https:\/\/sdna.lu\/index.php?rest_route=\/wp\/v2\/posts\/12767\/revisions"}],"predecessor-version":[{"id":12783,"href":"https:\/\/sdna.lu\/index.php?rest_route=\/wp\/v2\/posts\/12767\/revisions\/12783"}],"wp:attachment":[{"href":"https:\/\/sdna.lu\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=12767"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sdna.lu\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=12767"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sdna.lu\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=12767"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}