Provisioning Azure Virtual Machines to run SQL Server
0 likes1,631 views
The document provides guidance on provisioning SQL Server virtual machines in Azure, outlining essential components, configurations, and best practices to optimize performance. It includes recommendations for setup, such as enabling TCP/IP, configuring remote access, and managing database storage efficiently. Additionally, it offers links to resources and contact information for further assistance.
Provisioning Azure Virtual Machines to run SQL Server
- 1. Amit Banerjee Senior PFE Microsoft Corporation Provisioning SQL Server Virtual Machines in Azure
- 2. 2
- 3. 8/2/2014 3 Name the movie?
- 4. 8/2/2014 4
- 7. If you don’t deploy on time? 8/2/2014 7
- 8. If you don’t deploy on time? 8/2/2014 8
- 10. 8/2/2014 10
- 11. 8/2/2014 11
- 12. What do you get? 8/2/2014 12 • Database Engine, Analysis Services, Integration Services • Reporting Services (configured in Native mode) • AlwaysOn Availability Groups are available in SQL Server 2012 (or later) but need additional configuration • Replication, Full-Text and Semantic Extractions for Search (Semantic Extractions in SQL Server 2012 or later only) • Data Quality Services (SQL Server 2012 or later only) • Master Data Services (SQL Server 2012 or later only), but requires additional configuration and components. • PowerPivot for SharePoint is available (SQL Server 2012 or later only), but requires additional configuration • All tools • Client Tools Connectivity, Client Tools SDK, and SQL Client Connectivity SDK. • SQL Server Books Online, but requires configuration by using Help Viewer.
- 14. Essentials 8/2/2014 14 • Configure endpoints (if not done) • Enable TCP/IP • Configure the port for TCP protocol • Setup the WF firewall • Enabled mixed mode authentication and create a SQL Authenticated user* • Configure remote DAC • Configure Max Server Memory • Configure MAXDOP
- 15. What next? 8/2/2014 15 • Use minimum Standard Tier A2 for SQL Server VMs. • Keep the storage account and SQL Server VM in the same region. • Disable Azure geo- replication on the storage account. • Avoid using operating system or temporary disks for database storage or logging. • Avoid using Azure data disk caching options (caching policy = None). • Stripe multiple Azure data disks to get increased IO throughput. • Format with documented allocation sizes. .
- 16. What next? 8/2/2014 16 • Limit or disable autogrow on the database. • Disable autoshrink on the database. • Move all databases to data disks, including system databases. • Move SQL Server error log and trace file directories to data disks. • Apply SQL Server performance fixes. • Setup default locations. • Enable locked pages. • Backup directly to blob storage. Separate data and log file I/O paths to obtain dedicated IOPs for data and log. • Enable database page compression. • Enable instant file initialization for data files.
- 17. DEMO Up above the sky so high! 8/2/2014 17
- 18. Resources 8/2/2014 18 Azure Pricing Calculator http://azure.microsoft.com/en- us/pricing/calculator/?scenario=full Pricing Overview http://azure.microsoft.com/en-us/pricing/overview/ Getting started with a SQL Server VM on Azure http://msdn.microsoft.com/library/azure/dn133151.aspx SQL Server 2014 E-book http://blogs.msdn.com/b/microsoft_press/archive/2014/ 04/02/free-ebook-introducing-microsoft-sql-server- 2014.aspx Setting up a SQL Azure VM http://troubleshootingsql.com/2014/05/30/setting-up- sql-server-on-azure-for-testing/ Whitepaper: Performance Guidance for SQL Server VMs http://msdn.microsoft.com/library/azure/dn248436.aspx
- 19. Contact Information Blog: www.troubleshootingsql.com Twitter: @banerjeeamit Twitter: @TblshootingSQL Email: troubleshootingsql@outlook.com Facebook: www.facebook.com/TroubleshootingSQL
Editor's Notes
- #14: For changing the port number using NETSH command, the following can be used after replacing the placeholder with the appropriate port number: netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = <PORT NUMBER> remoteip = ANY profile = PUBLIC