Azure SQL Migrations using Azure Data Studio
This article looks at database migration with the Azure Data Studio extension, making it easy to move databases from an on premises SQL Server to one in Azure.
2021-09-20
6,945 reads
This article looks at database migration with the Azure Data Studio extension, making it easy to move databases from an on premises SQL Server to one in Azure.
2021-09-20
6,945 reads
2021-09-08
811 reads
2021-08-27
461 reads
2021-03-05
492 reads
2021-03-04
372 reads
2020-12-21
253 reads
2020-12-01
438 reads
2020-06-08
509 reads
The recommended way to backup and restore databases in Managed Instance is using built-in automatic backups and cross-instance point-in-time restore. However, if you need to use the manual backups, Jovan Popvic explains the procedure that you would need to follow.
2019-05-31
Jovan Popovic has some pieces of advice for backin...
2019-05-24
It’s been forgotten about and neglected for few years but I’ve decided to dust...
I am honored to announce that I have been renewed as a Microsoft MVP...
By Rohit Garg
Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...
Comments posted to this topic are about the item How a Legacy Logic Choked...
I have tried a number of times to export and then import my SSMS...
Hi I need to connect to a SQL server via FQDN - that is...
For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question: You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?
See possible answers