SQL Server Disk configuration settings are one of the most important aspects of SQL Server performance tuning. Typically, disks are one of the slowest parts of the entire SQL subsystem. Without proper disk configuration, SQL Server can slow down, increase locks and waits. It can also significantly increase the overall memory and CPU usage. In short, disk management and optimization are crucial for SQL Server performance. In this post, we are going to focus on just that. Read along to know more. [Read more…]
System Center contains a suite of products and enterprises who have investments in them deploy them together. However, there are restrictions when it comes to settings. Individual System Center products have different systems requirements, especially from the SQL Server perspective. Read below to know more about System Center Deployment restrictions for SQL Server. [Read more…]
In my previous post, we deployed SQL Server 2016 on a Windows Server 2012 R2 Operating system on Google Cloud. When you use the SQL Server Public Images, SQL Server and Windows Server Licensing cost are included in the billing. The default SQL Server instance is pre-installed and is bundled along with the Virtual Machine. This is very straightforward and pretty much assures that you are license compliant. But, how about bringing your own SQL licenses to Google Cloud? In a lot of scenarios, Customer would have already purchased SQL Server and is running active workloads on-premises. In order to bring your existing SQL Server licenses to the cloud, you need to follow certain guidelines. In this post, I am going to talk about how to license your SQL Server on Google Cloud. [Read more…]
Google Cloud Services recently added Microsoft SQL Server to its offerings. Google’s move is primarily due to a strong customer demand. The customer wants to run their existing mission critical apps on Google Cloud. Microsoft and Amazon already offer SQL Server on Azure and AWS respectively and Google is a late entrant. Since this is a welcome change, we decided to run SQL server VM (Virtual Machine) inside Google Cloud. In this post, I am going to talk about how to run Microsoft SQL Server 2016 on Google cloud step by step.
Running Microsoft SQL Server 2016 on Google
In order to begin, you would need to activate your Google Cloud account using a Credit Card. Even though the site instructions says it’s free, you would still be charged $1 on your credit card. Nonetheless, Google will graciously give you a $300 of credit to run your server workloads. Once you are logged into your Google Cloud Console, you would need to select the billing account details. Select your account from the drop-down list and proceed as given in the following screenshot:
Once the billing and Sign-In steps are out of the way, you can proceed with the VM creation process.
From the top left menu, Select > Compute Engine > VM Instances > Click “Create Instances”
On the “Create an Instance” page, you need to provide the following details:
- Name of the Instance
- Zone or Region (If you are from the Azure World)
- Select the Virtual CPU’s and System Memory from the”Machine Type” menu
- Under “Boot Disk” menu, Debian/Linux is selected by default. Click on Change as given in the following screenshot
For this example, We will be selecting “SQL Server 2016 Standard Edition on Windows Server 2012 R2“. For Disk options, we are selecting “SSD Persistent disk“. Currently, the max disk size supported is 65536 GB (65.536 TB).
Note that Enterprise Edition for any of the SQL Server versions is not available.
See the below Screenshot:
Once selected, Click on “Create VM” to complete the project. For this example, we have kept all the other options as default.
It took 4 seconds to create the VM from the image which I think is incredible.
Sure enough, the VM was up and running and the speed we felt was incredibly fast. A quick internet speed test shows a no compromise internet connection.
We ran a quick disk speed check with HD Tach and found the following results:
- Random Disk Access: 1.1 ms
- CPU Util: >5%
- Avg Read Speed: 143.1 Mbps
Performance is on par with what you would expect from a premium SSD-based storage disk. The numbers are similar to what you would get on Azure Virtual Machines (with Premium Storage) hosted by Microsoft.
Just like Azure, SQL Server 2016 was installed as a part of the image. You can also install SQL Server from the C:sql_server_install folder location. SQL Server Management Studio (SSMS) however was not installed, so we installed it from the Microsoft download site. We would investigate further into the performance aspects and post it later when we are ready with our findings.
For any comments for feedback, drop us a line below. Thanks!
All You Need To Know About The Windows 10 Anniversary Update and Issues
Windows 10 has been arguably the most successful Windows yet from Microsoft. With over 350 Million users at the time of this writing, it is currently the second most used operating system. The leader of the pack is the old and faithful Windows 7. However, things will change once the large enterprise accounts moves over to Windows 10. The Windows Anniversary update is the second major update post Windows 10 release back in 2015. Here is all you need to know about the Windows 10 Anniversary Update. [Read more…]
In my previous posts, I have already spoken about the best practices of Shrinking Log files and Database Files. From the recommendations, it is quite evident that Microsoft support strongly discourages you to perform any Database or Log shrink operations. Instead, follow all the best practices that is already mentioned in my previous posts. However, sometimes in a non production environment, you might want to do this as a one time activity. In this post I will explain how to shrink SQL server database log in Availability Groups using T-SQL. [Read more…]
How to Manage your SQL Server Log and Database File Size Growth
Managing the Database and log file size growth can be a difficult task sometimes. When things go out of hand, DBA tend to use inefficient methods such as “Database Shrink” or “Shrink Log Files“. Database shrink can hurt your SQL Server performance. Shrinking Log files will take away your option to do “Point in Time Restores”. So what are the best practices? Read on to know how to manage your SQL Server log and database file size growth. [Read more…]
How to Upgrade from Expired SQL Evaluation Edition
SQL Server Evaluation Edition is basically a full blown Enterprise Edition that you can run for 180 days. That is a good amount of time to test and evaluate your software and resolve performance issues before you actually decide to make a purchase. However there are a good number of customers who actually forget to upgrade the evaluation edition. When this happens, it becomes difficult to upgrade and recover your data. In this post, I am going to talk about how to upgrade from expired SQL evaluation edition and recover your data. [Read more…]
Shrink SQL Server Databases for Mirroring & Availability Groups
Shrinking SQL Server Databases and Log Files is a popular discussion among both experienced and entry level DBA‘s. Why? because data and log files can grow much bigger than expected and sometimes can run out of disk space. In case of High Availability deployments, you will have to run the databases under “Full Recovery Model” and that can cause your log files to grow as well. So the big question is, Should you shrink SQL Server databases for Mirroring and Availability Groups? Let’s find out! [Read more…]
How to Upgrade to SQL Server 2016 from Earlier and Older Versions
SQL Server 2016 comes with multiple components. Upgrade considerations for each one of them is different. Before upgrading, ensure that the features are still supported and not deprecated. In this post, I am consolidating a list and talk about how to upgrade to SQL Server 2016 from earlier and older versions. [Read more…]