Uploaded image for project: 'Solution Center'
  1. Solution Center
  2. SOL-264

EXASOL on Azure: Getting Started

    XMLWordPrintable

    Details

    • Type: How To
    • Status: Obsolete
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Solution:
      Hide

      Table of Contents

      This Getting Started guide covers the following initial steps:

      (1) Selecting an appropriate instance type
      (2) Attaching disks and finalizing the configuration
      (3) Logging into EXAoperation
      (4) Connecting using EXAplus

      (1) Selecting an appropriate instance type

      A good rule of thumb is that the RAM size of the selected instance should correspond to approximately 10% - 15 % of your raw data.

      For detailed Information on how to select an appropriate instance please refer to links provided in the corresponding section of the FAQ Solution document.

      We recommend that you use instance types of category D and G with >16 GB main memory.

      If we assume that your raw data (uncompressed) is about 300 GB in size, the following instances would be a good choice:

      • D12, 4 cores, 28 GB main memory
      • G1 1 cores, 28 GB main memory

      Please note:

      • We discourage the use of instance types A0-A4 and A8/A9 for technical reasons
      • The sizing "rule of thumb" used above may not be appropriate for your use case. Based on your specific use case, you may need significantly more memory
      • Different Azure instances use different hardware platforms and generations. Therefore the number of cores of different instance type should not be used as a performance indicator or for performance comparison.

      (2) Attaching disks and finalizing the configuration

      After your database instance has been successfully provisioned and started please connect to the instance via https (the IP address or the DNS name of your instance can retrieved from the management portal).
      Please use Firefox, Version 10.0+ to perform the configuration and to use EXAoperation, EXASOL's management tool.
      It may happen that you have to confirm the digital certificate first as its validity cannot be automatically verified by the web browser.

      If the CPU of the selected instance is not supported or the minimum amount of main memory is smaller than 4GB, a corresponding alert will be displayed.

      In these circumstances, it will not be possible to proceed. You will have to change the instance type in the Azure management console or delete the current instance and select an appropriate instance type.

      If you haven't connected any additional data disks to the instance, a warning will be shown that data will be stored on instance-local temporary disk space.
      This configuration is only recommended for testing purposes because data stored on local disk space won't be available after a shutdown of the instance .

      After attaching additional disks in the Azure management console, this warning will be replaced by information regarding the overall size of the attached persistent disk drives.

      Please note that it is not possible to extend the attached disk storage after finalizing this configuration.
      For recommendations regarding sizing of the persistent storage please refer to the FAQ.

      You have to set two passwords:

      1. EXAOperation password: This is the password for the user "admin" required to log into the EXAOperation management front-end
      2. EXASolution password: This is the password for the "sys" database user.

      Selecting "proceed" will start the database initialization. The may take a while based on the selected instance type and size.
      On successful database initialization, you will automatically be forwarded to the login screen of EXAoperation, EXASOL's management frontend.

      (3) Logging into EXAoperation

      Now you can log into EXoperation using the user name "admin" and the EXAoperation password you just defined.

      If everything went OK, you should now see that your EXASOL instance is running (green light).
      If the status of the current instance is yellow, the database is still starting up.
      In this case, please wait a moment and refresh the page.

      (4) Connecting to your database with EXAplus

      First download and install EXAplus, EXASOL's standard SQL client from EXASOL ( https://www.exasol.com/portal/display/DOWNLOAD/5.0)

      If you connect from outside the Azure virtual network (e.g. from your local PC), please make sure that port 8653, EXASOL's standard connection port, is available from "outside".
      As this port is not reachable by default you have to explicitly configure it in the ENDPOINTS section of you instance in the Azure management portal:

      • Select "Add a stand-alone endpoint"
      • Protocol=TCP; Internal Port:8653; External Port:8653
        (Of course you can select any other external portal number)

      For more information please refer to the manual and other information in the solution centre

      Show
      Table of Contents This Getting Started guide covers the following initial steps: (1) Selecting an appropriate instance type (2) Attaching disks and finalizing the configuration (3) Logging into EXAoperation (4) Connecting using EXAplus (1) Selecting an appropriate instance type A good rule of thumb is that the RAM size of the selected instance should correspond to approximately 10% - 15 % of your raw data. For detailed Information on how to select an appropriate instance please refer to links provided in the corresponding section of the FAQ Solution document. We recommend that you use instance types of category D and G with >16 GB main memory. If we assume that your raw data (uncompressed) is about 300 GB in size, the following instances would be a good choice: D12, 4 cores, 28 GB main memory G1 1 cores, 28 GB main memory Please note: We discourage the use of instance types A0-A4 and A8/A9 for technical reasons The sizing "rule of thumb" used above may not be appropriate for your use case. Based on your specific use case, you may need significantly more memory Different Azure instances use different hardware platforms and generations. Therefore the number of cores of different instance type should not be used as a performance indicator or for performance comparison. (2) Attaching disks and finalizing the configuration After your database instance has been successfully provisioned and started please connect to the instance via https (the IP address or the DNS name of your instance can retrieved from the management portal). Please use Firefox, Version 10.0+ to perform the configuration and to use EXAoperation, EXASOL's management tool. It may happen that you have to confirm the digital certificate first as its validity cannot be automatically verified by the web browser. If the CPU of the selected instance is not supported or the minimum amount of main memory is smaller than 4GB, a corresponding alert will be displayed. In these circumstances, it will not be possible to proceed. You will have to change the instance type in the Azure management console or delete the current instance and select an appropriate instance type. If you haven't connected any additional data disks to the instance, a warning will be shown that data will be stored on instance-local temporary disk space. This configuration is only recommended for testing purposes because data stored on local disk space won't be available after a shutdown of the instance . After attaching additional disks in the Azure management console, this warning will be replaced by information regarding the overall size of the attached persistent disk drives. Please note that it is not possible to extend the attached disk storage after finalizing this configuration. For recommendations regarding sizing of the persistent storage please refer to the FAQ. You have to set two passwords: EXAOperation password: This is the password for the user "admin" required to log into the EXAOperation management front-end EXASolution password: This is the password for the "sys" database user. Selecting "proceed" will start the database initialization. The may take a while based on the selected instance type and size. On successful database initialization, you will automatically be forwarded to the login screen of EXAoperation, EXASOL's management frontend. (3) Logging into EXAoperation Now you can log into EXoperation using the user name "admin" and the EXAoperation password you just defined. If everything went OK, you should now see that your EXASOL instance is running (green light). If the status of the current instance is yellow, the database is still starting up. In this case, please wait a moment and refresh the page. (4) Connecting to your database with EXAplus First download and install EXAplus, EXASOL's standard SQL client from EXASOL ( https://www.exasol.com/portal/display/DOWNLOAD/5.0 ) If you connect from outside the Azure virtual network (e.g. from your local PC), please make sure that port 8653, EXASOL's standard connection port, is available from "outside". As this port is not reachable by default you have to explicitly configure it in the ENDPOINTS section of you instance in the Azure management portal: Select "Add a stand-alone endpoint" Protocol=TCP; Internal Port:8653; External Port:8653 (Of course you can select any other external portal number) For more information please refer to the manual and other information in the solution centre
    • Category 1:
      Plattform Support - EXASOL on Azure

      Attachments

        Issue Links

        1. Config_Warning_Local_Storage.png
          Config_Warning_Local_Storage.png
          1.77 MB
        2. exaoperation-instance.png
          exaoperation-instance.png
          51 kB
        3. exaoperation-login.png
          exaoperation-login.png
          32 kB
        4. exaplus-connected.png
          exaplus-connected.png
          95 kB
        5. exaplus-connection.png
          exaplus-connection.png
          36 kB
        6. initializing.png
          initializing.png
          2.30 MB
        7. Persistent_Storage_Attached.png
          Persistent_Storage_Attached.png
          1.86 MB
        8. screenshot-config-alert.png
          screenshot-config-alert.png
          1.92 MB

          Activity

            People

            • Assignee:
              CaptainEXA Captain EXASOL
              Reporter:
              CaptainEXA Captain EXASOL
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: