The cloud phenomenon is no more a dream for many, but a reality for several customers I have been working with. Many of my customers are looking for guidance and from time to time I get an opportunity to have some deep constructive discussions. These discussions can range from should I be going to cloud or not, is this app cloud ready, can we do a lift-shift of this application directly to some cloud player etc. Though each of these discussions lead from one point to another, there is a lot of profiling I do with customers. In this blog, I want to talk about a conversation I had with one of my customers who was evaluating cloud for one of his applications. Let us see a Cloud Consulting Pre-Engagement Questionnaire.
SQL SERVER – Setting Firewall Settings With Azure SQL Server VMs
Recently I had a session around using SQL Server on Azure and during this session one of the questions was to access the SQL Server in a Hybrid Setup. This is a typical scenario wherein the developer was requesting to connect to the SQL Server running on a VM from his application that was sitting inside his environment. Though there were specific steps that needed to be taken, he was getting some error. Let us learn about how to setup firewall with Azure SQL Server VMs.
SQL SERVER – Unable to Create Listener for AlwaysOn Availability Group in Azure via Template Deployment
Recently I was trying to help a customer who was deploying AlwaysOn Availability Group in Microsoft Azure via template deployment. The template was failing with below error
SQL SERVER – How to Change SQL Server Collation on Microsoft Azure VM (IaaS)
I have been using Microsoft Azure, SQL Virtual Machine (IaaS) for quite some time because few of my clients ask questions about them. My clients generally use images from gallery to deploy SQL Server. Once they realized that they want to change the SQL Server collation instance. I was contacted to know the steps to do that. I learned something new so sharing via the blog.
Caution: Rebuild of system databases is as good as the fresh installation of SQL Server. YOU WOULD LOSE ALL EXISTING INFORMATION so please backup the stuff, if needed.
SQL SERVER – Introduction to SQL Azure Database Throttling
In standalone versions of SQL Server, if your SQL Server receives more concurrent requests than it can service simultaneously, it will queue the requests for later processing (subject to certain limits—generally available memory on the box). For example, if you have the max worker thread configuration option set to 100 and there are already 100 queries submitted to the server than any new requests are simply queued until one of the worker threads completes and can pick up the request. Except in fatal circumstances where DBA intervention is required this will allow all of the requests to eventually complete (or potentially timeout, if the client specified this setting). Let us understand about SQL Azure Database Throttling.