on-premises or Azure VMs to the fully-managed PaaS database service Azure SQL Database Managed Instance. In this post you will see how to create PowerShell scripts that automate migration to Managed Instance using Azure PowerShell and DbaTools.

PowerShell. This will require some way to get the information from PowerShell into SQL Server.

building!

how to use this command in this ATA Learning tutorial!

in worksheets. We can import from and export to SQL Excel data using a combination of ImportExcel and dbatools modules.

commands, and how you can run the assessments for your Azure SQL Managed Instances as well as your on-prem SQL Server instances.

possibly leave yourself open to SQL injection attacks. While you may be the only one using your script, it's likely that you're using values you're getting from a database, file, or some other external source. So I finally got around to writing a function that supports parameterised queries, and thought I'd offer it up in case others find it useful.

over 500 commands, this free and open source PowerShell module has the horsepower to automate just about every task you can imagine?and then some! Written by dbatools creator Chrissy LeMaire and dbatools advocate Rob Sewell, Learn dbatools in a Month of Lunches teaches you techniques that will make you more effective?and efficient?than you ever thought possible.

multiple processes in parallel. Everything seemed to work OK for a while, but then everything broke.

out SQL Servers. The chief time consuming task being when I'd have to move the SQL Server's default System Database and Log Files to new, dedicated database and log volumes.

example, maybe a guide or a source of ideas for your own implementation. This is about using publicly available software (like database clients or NuGet packages) and a few lines of PowerShell code to show database administrators how to work with PowerShell.

requested this feature be added to Azure Data Studio and it has become the most popular feature request for Notebooks. (Although, I'm sure it only became the most popular after they added copying from the results grid a few months ago )

via Exchange Web Services (EWS). Apparently there's a "wontfix" bug in Exchange, where a request to fetch email over this interface that can silently fail. The known workaround is to move email between folders in the affected account, which for some reason causes a state change of some kind that suddenly allows email to be handled again.

100,000 records from a table with 97 varchar(320) fields in an Azure SQL HyperScale database. Following, I would like to share my lessons learned here.

errors. The version, startup parameters, memory settings and a ton more. I've been working with SQL Server for over 20 years and I still see messages in the errorlog that I don't remember coming across.

options

restores the database from a .bak file to a differently named database.

more than I wanted to add as an array or hash table in script, or even an external file like an XML document. So I searched for a portable, standalone database that I could distribute with the script and happened across LiteDB, a lightweight, single-file NoSQL database. It seemed the ideal solution as there's a .Net code library for it, and so far I'm pretty impressed.

run Ola's Index Optimize and Statistics Updates on them. All of these have seemed way too complicated probably because I was setting them up once, not again for several more months or a year. Well