This blog post is not about which User Interface is better, Classic or Snowsight – If anyone does want my feedback on what I like and don’t like about them then I might do another blog post but the aim here today is to show you how to load the classic one as the default experience because when you login to snowflake the snowsight UI is the default one..
Storage Accounts are pretty much integrated into so many different designs in Azure, whether you are using Azure Synapse, 3rd party product like Snowflake, or Event Streaming designs – we need it.
I really like scale sets. It lets you create and manage up to 1000 load balanced VMs per availability zone using windows or Linux images. (We can have flexible or uniforms modes for orchestration which dictates if you go down the homogenous VM route or a mix, where a mix is the flexible option.
There are many different family groups for Azure VMs each with its own purpose. Below is a summary of what can be selected. This is important because for example if you are running complex OLTP database servers then very likely you will go for Memory optimised machines, right? We know SQL server loves RAM. Any ways here is the list:
Lets write about Microsoft Azure, specially the area of high availability when it comes to virtual machines.
A post close to my heart, Azure SQL Managed Instance, I have blogged about this many times but I feel I should be sharing more details about this. One important topic – Maintenance windows.
The query store, sounds familiar? The idea of the black box sitting within the database server watching what is going on within the environment. This is available within MySQL, maybe not as feature rich as SQL Server but still useful.
You will find this option under the Query performance insight section of your MySQL server.
If you have used MySQL before you will know about the system server variables, you know such commands as SHOW VARIABLES; You can access most of them via the Azure portal or connect to MySQL and issues the commands you come to know about.
When it comes to MySQL and storage you will normally have to decide on 3 options: basic, general purpose v1 or v2.
Basic does support up to 1TB and is low-cost option but has no IOPs guarantee, not really recommended for production systems. General purpose v2 should be the one used because it uses latest storage infrastructure which can support up to 16-TB and 20000 IOPs a shown below.
We have already created the server now it’s time to connect to it. What you will need – connection string details, correct networking setup and a tool like MySQL Workbench.
All About Data 