Blog Pro de Jean-Baptiste HEREN - Tag - SQL Server Notes d'un consultant Freelance en Informatique 2015-11-03T21:34:19+01:00 JB HEREN urn:md5:e39389b5ec134d99645112fce3d957df Dotclear Analysis Services 2005 : L'erreur système suivante s'est produite : . urn:md5:ea963c23ec708d8a1a15c7a70946830e 2011-01-24T16:39:00+01:00 2011-01-25T13:41:59+01:00 Jean-Baptiste Heren Décisionnel Analysis ServicesSQL ServerSQL Server 2005 <p>Voici une astuce pour SSAS sous SQL Server 2005. Si vous rencontrez l'erreur&nbsp;:</p> <pre>[script] L'erreur système suivante s'est produite : . </pre> <p>Cette erreur est liée à la présence au niveau de l'onglet Membership des rôles Analysis Services, de membres n'existant plus dans Active Directory.</p> <p>Il suffit donc nettoyer vos rôles :)</p> SSAS Batch Processing with XMLA urn:md5:bacb36c93507c36da0b994e099f7e2cf 2009-11-09T12:10:00+01:00 2009-11-13T12:01:52+01:00 Jean-Baptiste Heren Décisionnel Analysis ServicesBusiness IntelligenceSQL ServerSSAS <p>When you want to schedule the processing of SSAS database (using Sql Server jobs), you have two options :</p> <ul> <li>create ans SSIS package containing Analysis services tasks &amp; schedule it.</li> <li>Build ans XMLA script &amp; schedule it.</li> </ul> <br /> Here we will see how you can build an XML script describing the processing tasks you want to execute. <h2>1- Buiding &amp; testing the script</h2> In Sql Server management studio, connect to yous SSAS database.<br /> <a href="http://blog.jbheren.com/public/Decisionnel/XMLA/04_-_Sql_Server_management_studio_-_connect_Analysis_services.jpg"> <img title="04_-_Sql_Server_management_studio_-_connect_Analysis_services.jpg, nov. 2009" alt="" src="http://blog.jbheren.com/public/Decisionnel/XMLA/04_-_Sql_Server_management_studio_-_connect_Analysis_services.jpg" /> </a><br /> <br /> Open a new XMLA Query window &amp; paste the following script in it.<br /> <br />  <a href="http://blog.jbheren.com/public/Decisionnel/XMLA/07_-_Sql_Server_management_studio_-_new_Query_XMLA.jpg"><img title="07_-_Sql_Server_management_studio_-_new_Query_XMLA.jpg, nov. 2009" alt="" src="http://blog.jbheren.com/public/Decisionnel/XMLA/.07_-_Sql_Server_management_studio_-_new_Query_XMLA_m.jpg" /></a><br /> <br /> <blockquote> <p>&lt;Batch ProcessAffectedObjects=&quot;true&quot; xmlns=&quot;http://schemas.microsoft.com/analysisservices/2003/engine&quot;&gt;<br />   <strong>&lt;Process</strong> xmlns:xsd=&quot;http://www.w3.org/2001/XMLSchema&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xmlns:ddl2=&quot;http://schemas.microsoft.com/analysisservices/2003/engine/2&quot; xmlns:ddl2_2=&quot;http://schemas.microsoft.com/analysisservices/2003/engine/2/2&quot;&gt;<br />     &lt;Object&gt;<br />       &lt;DatabaseID&gt;<strong>ASdatabase</strong>&lt;/DatabaseID&gt;<br />       &lt;DimensionID&gt;<strong>Dimension ID(not name)</strong>&lt;/DimensionID&gt;<br />     &lt;/Object&gt;<br />     &lt;Type&gt;ProcessFull&lt;/Type&gt;<br />     &lt;WriteBackTableCreation&gt;UseExisting&lt;/WriteBackTableCreation&gt;<br />   <strong>&lt;/Process&gt;</strong><br />   <strong>&lt;Process&gt;</strong><br />     &lt;Object&gt;<br />       &lt;DatabaseID&gt;<strong>ASdatabase</strong>&lt;/DatabaseID&gt;<br />     &lt;DimensionID&gt;<strong>Dimension 2 ID</strong>&lt;/DimensionID&gt;<br />   &lt;/Object&gt;<br />   &lt;Type&gt;ProcessFull&lt;/Type&gt;<br />   &lt;WriteBackTableCreation&gt;UseExisting&lt;/WriteBackTableCreation&gt;<br /> <strong>&lt;/Process&gt;</strong><br /> <strong>&lt;Process&gt;</strong><br />   &lt;Object&gt;<br />     &lt;DatabaseID&gt;<strong>ASdatabase</strong>&lt;/DatabaseID&gt;<br />     &lt;CubeID&gt;<strong>Cube ID</strong>&lt;/CubeID&gt;<br />   &lt;/Object&gt;<br />   &lt;Type&gt;ProcessFull&lt;/Type&gt;<br />   &lt;WriteBackTableCreation&gt;UseExisting&lt;/WriteBackTableCreation&gt;<br /> <strong>&lt;/Process&gt;</strong><br /> &lt;/Batch&gt;</p> </blockquote> <br /> Of course, you just have to set your own database and dimensions/cubes IDs. You can add as many &lt;process&gt;&lt;/process&gt; blocks you need.<br /> Now just run your Script and see what happens.<br /> <br /> <h2>2- Scheduling</h2> When you are ready, create or open ans Sql job under SQL Server Agent.<br /> <a href="http://blog.jbheren.com/public/Decisionnel/XMLA/01_-_Sql_Server_management_studio_-_create_new_job.jpg"> <img title="01_-_Sql_Server_management_studio_-_create_new_job.jpg, nov. 2009" alt="" src="http://blog.jbheren.com/public/Decisionnel/XMLA/.01_-_Sql_Server_management_studio_-_create_new_job_m.jpg" /> </a><br /> <br /> add a step to your job, choose &quot;SQL Server Analysis Services&quot; as Type &amp; paste your script.<br /> <a href="http://blog.jbheren.com/public/Decisionnel/XMLA/03_-_Sql_Server_management_studio_-_step_properties.jpg"> <img title="03_-_Sql_Server_management_studio_-_step_properties.jpg, nov. 2009" alt="" src="http://blog.jbheren.com/public/Decisionnel/XMLA/.03_-_Sql_Server_management_studio_-_step_properties_m.jpg" /> </a><br /> <br /> Of course this is just a Quickstart. For more informations about XMLA structure &amp; options, just refer to the MSDN Help.