Exportera (0) Skriv ut
Visa allt
EN
Det här innehållet finns inte tillgängligt på ditt språk men här finns den engelska versionen,

Finish Setup for SQL Server Data Warehouse in Azure Virtual Machines

Updated: October 13, 2013

Follow these simple instructions to finish setting up your optimized SQL Server data warehouse after you have provisioned one of the following images from the Virtual Machine Gallery.

  • SQL Server 2012 SP1 for Data Warehousing on WS 2012

  • SQL Server 2014 CTP2 Evaluation for Data Warehousing on WS 2012

Let’s get started – to finish setting up your optimized data warehouse:

Step 1: Attach Disks

Skip this step if you provisioned your optimized data warehousing virtual machine by using the New-AzureSqlDwIaasVM PowerShell script. For more information, see Provision the SQL Server for data warehousing Virtual Machine.

Now that you have provisioned your optimized data warehousing virtual machine, you need to attach the disks. To do this, you can use the Management Portal or PowerShell cmdlets. Whichever method you choose, remember these things when attaching disks:

  1. Attach only EMPTY disks that are 1023 GB in size. Note: You will be charged only for the used portion of the disks.

  2. Verify the Host Cache Preference is set to NONE.

  3. Attach the required number of disks shown in the following table, according to the virtual machine size you selected.

    Number of disks to attach

    Notes:

    1. Size A5 is not supported for the SQL Server 2012 image.

    2. Size A6 is recommended for the SQL Server 2012 image.

    3. Size A7 is recommended for the SQL Server 2014 image.

  4. You can attach up to the maximum number of disks allowed for each virtual machine size. However, the data warehousing optimizations will only be configured on the number of disks in the above table. You can use extra disks for other purposes such as storing backups.

To attach disks by using the portal

  1. Go back to the Management Portal and select your virtual machine.

    Attach Disks to Data Warehouse Virtual Machine
  2. Attach an empty disk. To do this, click Attach and select Attach Empty Disk.

    Attach Disks to Data Warehouse Virtual Machine
  3. Enter 1023 for the SIZE (GB) setting, verify Host Cache Preference is None, and click the checkmark.

    Attach Disks to Data Warehouse Virtual Machine
  4. Watch the progress of the disk attachment in the Management Portal until the status is Running with a checkmark.

  5. Repeat the attach disk process for the number of required disks for your virtual machine size.

  6. Now that all disks are attached, the virtual machine will start to configure the data warehousing optimizations. Continue to Step 2: Verify Data Warehousing Optimizations Complete Successfully.

To attach disks by using cmdlets

  1. Before you begin, install and configure PowerShell on your Windows client.

  2. Open a PowerShell window and perform the next steps from the PowerShell prompt.

  3. Before you can connect for the first time, you need to import a certificate to the virtual machine for authentication.

    1. Run this cmdlet to generate a certificate for authentication to your virtual machine. As part of this step, you will be prompted to login to the Management Portal if you are not already logged in. Then the portal will ask you to save the publishsettings file which contains your certificate. Save the file to your Windows client.

      PS C:\>get-AzurePublishSettingsFile
      
      
    2. Run this cmdlet to import the certificate. Enter the full path and name of your publishsettings file.

      PS C:\>import-AzurePublishSettingsFile "<myPublishSettingFileName>.publishsettings”
      
  4. Run this cmdlet to set the current subscription for the session to your subscription and to set your current storage account.

    PS C:\> Set-AzureSubscription –SubscriptionName "<mySubscriptionName>" -CurrentStorageAccount "<myStorageAccount>"
    
    
  5. Run this cmdlet to attach the disks. Attach the number of disks required for the virtual machine size you selected. This example attaches five disks, which is the number of disks required for the A6 size.

    If you have already attached one or more disks by using the Management Portal, you do not need to specifiy the LUN number; will assign each disk the next available LUN number.

    PS C:\> Get-AzureVM –ServiceName "<mysvc>" -Name "<myVM>" |
        Add-AzureDataDisk –CreateNew –DiskSizeInGB 1023 –HostCaching None –DiskLabel "<myVM-d1>" –LUN 0 |
        Add-AzureDataDisk –CreateNew –DiskSizeInGB 1023 –HostCaching None –DiskLabel "<myVM-d2>" –LUN 1 |
        Add-AzureDataDisk –CreateNew –DiskSizeInGB 1023 –HostCaching None –DiskLabel "<myVM-d3>" –LUN 2 |
        Add-AzureDataDisk –CreateNew –DiskSizeInGB 1023 –HostCaching None –DiskLabel "<myVM-d4>" –LUN 3 |
        Add-AzureDataDisk –CreateNew –DiskSizeInGB 1023 –HostCaching None –DiskLabel "<myVM-d5>" –LUN 4 |
        Update-AzureVM
    
    
  6. Verify the disks have attached successfully. To do this you can monitor the progress by viewing a log file.

    To verify the disks have attached successfully

    1. Use Remote Desktop to connect to the virtual machine.

    2. Locate the C:\Program Files\Microsoft SQL Server\DwIaas\Log folder. If you look in this folder before you have started to attach disks, you will see a message similar to the following at the end of the latest log file.

      Waiting on new EMPTY disk size 1023 GB to be attached…; 0 out of 5 are detected.

      After each additional disk is attached new messages are displayed at the end of the log file.

      Waiting on new EMPTY disk size 1023 GB to be attached…; 1 out of 5 are detected.
      Waiting on new EMPTY disk size 1023 GB to be attached…; 2 out of 5 are detected.
      Waiting on new EMPTY disk size 1023 GB to be attached…; 3 out of 5 are detected.
      Etc.
    3. Now that all disks are attached, the virtual machine will start to configure the data warehousing optimizations. Continue to Step 2: Verify Data Warehousing Optimizations Complete Successfully.

Step 2: Verify Data Warehousing Optimizations Complete Successfully

After all of the disks are attached, the virtual machine will automatically start to configure the SQL Server data warehousing optimizations. Wait for this process to complete. It usually takes between 5 and 10 minutes; when loads are high it can take as much as 30 minutes.

noteNote
You should not login to SQL Server until the data warehousing optimizations have completed successfully.

To verify the optimizations

  1. Connect to the virtual machine by using remote desktop.

    To connect With Remote Desktop

    1. Open the Management Portal.

    2. Click VIRTUAL MACHINES.

    3. If your virtual machine is not highlighted, click on the virtual machine, somewhere other than the name column, to highlight it.

    4. Click the CONNECT icon at the bottom of the virtual machines window

    5. management Portal will ask you to open or save an RDP file. Click open. This initiates a remote desktop connection to your virtual machine.

    6. At the Remote Desktop login prompt, enter your password to login.

  2. Watch for a second shortcut to appear on the virtual machine desktop. This indicates the optimizations have complete. Both shortcuts on the desktop link to the documentation on MSDN.

  3. To verify the optimizations have completed successfully, view the Summary.txt file in the Program Files\Microsoft Sql Server\DwIaas\Log folder. The Summary.txt file should show Final result: Passed, which means the optimizations completed successfully. The following shows an example of some lines in the Summary.txt file. The details are written to the same ConfigDWDetail.txt file that contains the attach disk progress.

    Summary.txt (not the entire file)

    Final result: Passed
    Start time: 09-17-2013 01:54:02
    End time: 09-17-2013 01:59:34
    Requested action: ConfigureDwIaasVm
    XML config file: C:\Program Files\Microsoft SQL Server\DwIaas\DwIaasConfigGeneral.xml
    Detailed Log file: C:\Program Files\Microsoft SQL Server\DwIaas\Log\09-17-2013-01-54- 02\ConfigDWDetail.txt
  4. If Summary.txt contains an error or if an error occurs while the optimizations are running, you must resolve the error before using SQL Server in the virtual machine. The simplest way to recover from an error is to delete the virtual machine and the disks, and start over. Alternatively, you can try to fix the error without starting over.

    To fix an error

    1. Restart the virtual machine.

    2. Use Remote Desktop to connect to the virtual machine.

    3. Open a PowerShell window on the virtual machine and run the script C:\Program Files\Microsoft SQL Server\DwIaas\ConfigDWIaasVM.ps1

    4. If this does not resolve the error, use the New-AzureSqlDWIaasVM PowerShell script to provision the virtual machine which automates the provisioning process and attaches the disks. For instructions, see Provision the SQL Server for data warehousing Virtual Machine.

Step 3: Disable Geo-replication

Set Geo-replication to OFF in the storage account that you used to attach the disks. Geo Redundant Storage is enabled by default for all existing storage accounts in production today.

To disable Geo-replication

  1. Open the Management Portal.

  2. From the menu items, click Storage.

  3. In the Storage window, under the Name column, click on the name of your storage account.

  4. In your storage account window, find the menu items towards the top of the window and click Configure.

  5. In the configuration settings, find the GEO-REPLICATION setting and click OFF.

For more information, see turning off geo-replication in the portal for your accounts.

Step 4: Start Using Your Optimized Data Warehouse

Congratulations! You are now ready to start using your optimized data warehouse. For recommendations on how to achieve the best results, see SQL Server Data Warehousing in Azure Virtual Machines.

Gruppinnehåll

Lägg till
Visa:
© 2014 Microsoft