Clustering SSAS












1















We are using both SQL Server 2012 and 2014 always on.



Here is my issue: we have an application that I have set up to use Availability groups(2014), however the issue I am having is that it uses SSAS and as far as I can tell I cannot set up the SSAS database to be akin to an availability group which floats between two replicas based on the av listener name/IP.



My hope was to have the SSAS database failover to the same replica that the databases would in case of a failover. Is this even possible and would you be able to point me to any articles.



I am referring to the OLAP database that appears under databases when you connect to SSAS through the GUI.










share|improve this question
















bumped to the homepage by Community 12 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • I've never had the need to cluster or account for HA on my OLAP database, but maybe this helps.msdn.microsoft.com/en-us/library/hh967523(v=sql.120).aspx

    – Jason B.
    Jul 15 '16 at 16:57
















1















We are using both SQL Server 2012 and 2014 always on.



Here is my issue: we have an application that I have set up to use Availability groups(2014), however the issue I am having is that it uses SSAS and as far as I can tell I cannot set up the SSAS database to be akin to an availability group which floats between two replicas based on the av listener name/IP.



My hope was to have the SSAS database failover to the same replica that the databases would in case of a failover. Is this even possible and would you be able to point me to any articles.



I am referring to the OLAP database that appears under databases when you connect to SSAS through the GUI.










share|improve this question
















bumped to the homepage by Community 12 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • I've never had the need to cluster or account for HA on my OLAP database, but maybe this helps.msdn.microsoft.com/en-us/library/hh967523(v=sql.120).aspx

    – Jason B.
    Jul 15 '16 at 16:57














1












1








1








We are using both SQL Server 2012 and 2014 always on.



Here is my issue: we have an application that I have set up to use Availability groups(2014), however the issue I am having is that it uses SSAS and as far as I can tell I cannot set up the SSAS database to be akin to an availability group which floats between two replicas based on the av listener name/IP.



My hope was to have the SSAS database failover to the same replica that the databases would in case of a failover. Is this even possible and would you be able to point me to any articles.



I am referring to the OLAP database that appears under databases when you connect to SSAS through the GUI.










share|improve this question
















We are using both SQL Server 2012 and 2014 always on.



Here is my issue: we have an application that I have set up to use Availability groups(2014), however the issue I am having is that it uses SSAS and as far as I can tell I cannot set up the SSAS database to be akin to an availability group which floats between two replicas based on the av listener name/IP.



My hope was to have the SSAS database failover to the same replica that the databases would in case of a failover. Is this even possible and would you be able to point me to any articles.



I am referring to the OLAP database that appears under databases when you connect to SSAS through the GUI.







sql-server clustering ssas






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 16 '16 at 7:17









Tom V

13.8k74677




13.8k74677










asked Jul 15 '16 at 16:51









user100244user100244

82




82





bumped to the homepage by Community 12 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 12 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • I've never had the need to cluster or account for HA on my OLAP database, but maybe this helps.msdn.microsoft.com/en-us/library/hh967523(v=sql.120).aspx

    – Jason B.
    Jul 15 '16 at 16:57



















  • I've never had the need to cluster or account for HA on my OLAP database, but maybe this helps.msdn.microsoft.com/en-us/library/hh967523(v=sql.120).aspx

    – Jason B.
    Jul 15 '16 at 16:57

















I've never had the need to cluster or account for HA on my OLAP database, but maybe this helps.msdn.microsoft.com/en-us/library/hh967523(v=sql.120).aspx

– Jason B.
Jul 15 '16 at 16:57





I've never had the need to cluster or account for HA on my OLAP database, but maybe this helps.msdn.microsoft.com/en-us/library/hh967523(v=sql.120).aspx

– Jason B.
Jul 15 '16 at 16:57










2 Answers
2






active

oldest

votes


















0














There is nothing like AlwaysOn for SSAS databases.



If you want high availability for your SSAS databases you need to set up a Windows Server failover cluster.



Refer to the documentation for instructions:




One approach for meeting your organization’s high availability
requirements for Analysis Services is to install it on a Windows
Server failover cluster (WSFC). A WSFC is composed of multiple servers
that offer redundancy in the event of a hardware failure, system
crash, or some other service disruption. A WSFC can offer protection
of your mission critical backend servers, including the Analysis
Services instances running your BI workloads.







share|improve this answer































    0














    I realise this is an old question, but you could solve this by scaling out Analysis Services. This technet article from 2005 is still relevant to SSAS 2016.



    Basically you process the cube on one server, and synchronize it to the other server. Synchronizing will only copy the changes, making it generally smaller and faster than a backup/restore. You can automate it with a simple XMLA script.



    The final part of this is to redirect traffic on a failover. You could do this by changing the connection string in your app (you might be able to change it dynamically) or using a DNS CName (just change where it points to and flush dns). Both require manual intervention. You could look at some sort of load balancing, which could then automate and only send requests to an active server.



    The other advantage of this, is you can allow the cube to be queried at the same time as dimensions/measure groups are being processed.



    You will need to think about licensing. If you are actively querying both, then both servers will need to be licensed. We have not had a problem with keeping a synchronized cube at our DR site that isn't queried, it was considered to be covered by Software Assurance, but you'll need to speak to a licensing expert to confirm your setup.






    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "182"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f144026%2fclustering-ssas%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0














      There is nothing like AlwaysOn for SSAS databases.



      If you want high availability for your SSAS databases you need to set up a Windows Server failover cluster.



      Refer to the documentation for instructions:




      One approach for meeting your organization’s high availability
      requirements for Analysis Services is to install it on a Windows
      Server failover cluster (WSFC). A WSFC is composed of multiple servers
      that offer redundancy in the event of a hardware failure, system
      crash, or some other service disruption. A WSFC can offer protection
      of your mission critical backend servers, including the Analysis
      Services instances running your BI workloads.







      share|improve this answer




























        0














        There is nothing like AlwaysOn for SSAS databases.



        If you want high availability for your SSAS databases you need to set up a Windows Server failover cluster.



        Refer to the documentation for instructions:




        One approach for meeting your organization’s high availability
        requirements for Analysis Services is to install it on a Windows
        Server failover cluster (WSFC). A WSFC is composed of multiple servers
        that offer redundancy in the event of a hardware failure, system
        crash, or some other service disruption. A WSFC can offer protection
        of your mission critical backend servers, including the Analysis
        Services instances running your BI workloads.







        share|improve this answer


























          0












          0








          0







          There is nothing like AlwaysOn for SSAS databases.



          If you want high availability for your SSAS databases you need to set up a Windows Server failover cluster.



          Refer to the documentation for instructions:




          One approach for meeting your organization’s high availability
          requirements for Analysis Services is to install it on a Windows
          Server failover cluster (WSFC). A WSFC is composed of multiple servers
          that offer redundancy in the event of a hardware failure, system
          crash, or some other service disruption. A WSFC can offer protection
          of your mission critical backend servers, including the Analysis
          Services instances running your BI workloads.







          share|improve this answer













          There is nothing like AlwaysOn for SSAS databases.



          If you want high availability for your SSAS databases you need to set up a Windows Server failover cluster.



          Refer to the documentation for instructions:




          One approach for meeting your organization’s high availability
          requirements for Analysis Services is to install it on a Windows
          Server failover cluster (WSFC). A WSFC is composed of multiple servers
          that offer redundancy in the event of a hardware failure, system
          crash, or some other service disruption. A WSFC can offer protection
          of your mission critical backend servers, including the Analysis
          Services instances running your BI workloads.








          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Aug 9 '16 at 11:46









          Tom VTom V

          13.8k74677




          13.8k74677

























              0














              I realise this is an old question, but you could solve this by scaling out Analysis Services. This technet article from 2005 is still relevant to SSAS 2016.



              Basically you process the cube on one server, and synchronize it to the other server. Synchronizing will only copy the changes, making it generally smaller and faster than a backup/restore. You can automate it with a simple XMLA script.



              The final part of this is to redirect traffic on a failover. You could do this by changing the connection string in your app (you might be able to change it dynamically) or using a DNS CName (just change where it points to and flush dns). Both require manual intervention. You could look at some sort of load balancing, which could then automate and only send requests to an active server.



              The other advantage of this, is you can allow the cube to be queried at the same time as dimensions/measure groups are being processed.



              You will need to think about licensing. If you are actively querying both, then both servers will need to be licensed. We have not had a problem with keeping a synchronized cube at our DR site that isn't queried, it was considered to be covered by Software Assurance, but you'll need to speak to a licensing expert to confirm your setup.






              share|improve this answer




























                0














                I realise this is an old question, but you could solve this by scaling out Analysis Services. This technet article from 2005 is still relevant to SSAS 2016.



                Basically you process the cube on one server, and synchronize it to the other server. Synchronizing will only copy the changes, making it generally smaller and faster than a backup/restore. You can automate it with a simple XMLA script.



                The final part of this is to redirect traffic on a failover. You could do this by changing the connection string in your app (you might be able to change it dynamically) or using a DNS CName (just change where it points to and flush dns). Both require manual intervention. You could look at some sort of load balancing, which could then automate and only send requests to an active server.



                The other advantage of this, is you can allow the cube to be queried at the same time as dimensions/measure groups are being processed.



                You will need to think about licensing. If you are actively querying both, then both servers will need to be licensed. We have not had a problem with keeping a synchronized cube at our DR site that isn't queried, it was considered to be covered by Software Assurance, but you'll need to speak to a licensing expert to confirm your setup.






                share|improve this answer


























                  0












                  0








                  0







                  I realise this is an old question, but you could solve this by scaling out Analysis Services. This technet article from 2005 is still relevant to SSAS 2016.



                  Basically you process the cube on one server, and synchronize it to the other server. Synchronizing will only copy the changes, making it generally smaller and faster than a backup/restore. You can automate it with a simple XMLA script.



                  The final part of this is to redirect traffic on a failover. You could do this by changing the connection string in your app (you might be able to change it dynamically) or using a DNS CName (just change where it points to and flush dns). Both require manual intervention. You could look at some sort of load balancing, which could then automate and only send requests to an active server.



                  The other advantage of this, is you can allow the cube to be queried at the same time as dimensions/measure groups are being processed.



                  You will need to think about licensing. If you are actively querying both, then both servers will need to be licensed. We have not had a problem with keeping a synchronized cube at our DR site that isn't queried, it was considered to be covered by Software Assurance, but you'll need to speak to a licensing expert to confirm your setup.






                  share|improve this answer













                  I realise this is an old question, but you could solve this by scaling out Analysis Services. This technet article from 2005 is still relevant to SSAS 2016.



                  Basically you process the cube on one server, and synchronize it to the other server. Synchronizing will only copy the changes, making it generally smaller and faster than a backup/restore. You can automate it with a simple XMLA script.



                  The final part of this is to redirect traffic on a failover. You could do this by changing the connection string in your app (you might be able to change it dynamically) or using a DNS CName (just change where it points to and flush dns). Both require manual intervention. You could look at some sort of load balancing, which could then automate and only send requests to an active server.



                  The other advantage of this, is you can allow the cube to be queried at the same time as dimensions/measure groups are being processed.



                  You will need to think about licensing. If you are actively querying both, then both servers will need to be licensed. We have not had a problem with keeping a synchronized cube at our DR site that isn't queried, it was considered to be covered by Software Assurance, but you'll need to speak to a licensing expert to confirm your setup.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 14 at 1:32









                  GregGreg

                  1,82022042




                  1,82022042






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Database Administrators Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f144026%2fclustering-ssas%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      الفوسفات في المغرب

                      Four equal circles intersect: What is the area of the small shaded portion and its height

                      جامعة ليفربول