Azure DB for MySQL – Storage v1 vs v2
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...
2022-02-07
17 reads
Arun Sirpal
Connecting to Single Server MySQL
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...
2022-02-03
19 reads
Creating Azure DB for MySQL – Single Server
Enough of the theory and text lets use the Azure Portal and create MySQL Single server. Navigate to the Azure Portal, find Azure Database for MySQL servers: Click create...
2022-01-31
39 reads
Azure DB for MySQL – Single server vs Flexible
When you start the build process for MySQL you will be shown the below screen, the question is what option would you select? It really does depend; I don’t...
2022-01-19
388 reads
Azure Database for MySQL
SQL Server is not the only database you build and deploy into Azure. Another very popular option is MySQL. Going back many years, this was actually my first database...
2022-01-11
56 reads
SQL Managed Instances – Failing Over
This is our current setup shown below. There is not much to failing over with Managed Instances, from experience it is similar to that of Azure SQL Database. Let’s...
2021-12-17 (first published: 2021-12-07)
266 reads
SQL Managed Instances – Cross Instance?
There is a setting / feature in Managed Instance worth talking about, it is called SQL Trust Groups. What is this? At a basic level it’s a way to...
2021-12-15
99 reads
SQL Managed Instance – Failover Groups Quick Tips
Lets summarise some important learnings about SQL MI and failover groups. when you add a database to a failover group the secondary database has the same edition / compute...
2021-12-09
129 reads
Failover Groups for Managed Instances
If you have been following me for a while you will know that I really like the Fail over groups within Azure SQL DB and it is no different...
2021-11-22
14 reads
Azure SQL Managed Instance – Premium Tier
In case you are not aware Microsoft have now deployed a new change to SQL Managed Instances within the tier types. In certain regions ( shown later) you can...
2021-11-10
138 reads
Blogs
Flyway Tips: AI Deployment Script Descriptions
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
A New Word: Fawtle
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
Post-quantum key exchange – Insurance policy for your packets
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
Forums
Where Your Value Separates You from Others
Comments posted to this topic are about the item Where Your Value Separates You...
Fixing the Error
Comments posted to this topic are about the item Fixing the Error
T-SQL in SQL Server 2025: Encoding Functions
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
Question of the Day
Fixing the Error
On SQL Server 2025, I have a database that has this collation: SQL_Latin1_General_CP1_CI_AS. I decide I want to run this code:
SELECT UNISTR('*3041*308A*304C*3068 and good night', '*') AS 'A Classic';
I get this error:Msg 9844, Level 16, State 4, Line 24 The char/varchar input type uses an unsupported collation. Only a UTF8 collation is supported with char/varchar input type in UNISTR function.What is the easiest way to fix this error? See possible answers