Migration

Test-DbaMigrationConstraint

Claudio Silva (@ClaudioESSilva)

Test-DbaMigrationConstraint View Source Claudio Silva (@ClaudioESSilva) Windows, Linux, macOS Synopsis Validates database migration compatibility between SQL Server instances by checking for edition-specific features. Description Prevents migration failures by identifying databases that use features incompatible with the destination SQL Server edition. This function queries sys.dm_db_persisted_sku_features to detect enterprise-level features that would cause migration issues when moving from higher editions (Enterprise/Developer) to lower ones (Standard/Express). Common migration scenarios this helps validate include moving databases from development environments running Developer edition to production Standard edition, or consolidating databases from Enterprise to Standard during license optimization.

SQL Server Migration Enhancements

Chrissy LeMaire

A while back, I added some new features to our migration commands but I forgot to blog about them. Then, I used one of the new features for a fast and successful migration, got so pumped and had to share. Multiple Destinations Now, you can migrate from one server to many. This applies to both Start-DbaMigration and all of the Copy-Dba* commands, including Copy-DbaDatabase and Copy-DbaLogin. As you may be able to see in the title bar of this Out-GridView, I am migrating from workstation, which is a SQL Server 2008 instance, to localhost\sql2016 and localhost\sql2017.

Real-World TDE Database Migrations

In today’s post, I will tell you about how we managed to successfully complete a migration during a ~12 hour maintenance window. This could have taken a LOT longer if we didn’t have dbatools to automate several of the steps. Although I will not go in to every detail about our process, I want to emphasize the areas were we chose to use dbatools to make our lives easier. The Goal Recently, we got the green light for upgrading to SQL Server 2016 and we were ready to roll.

Scheduling a Migration

Chrissy LeMaire

Hey, Chrissy here. Recently, I had great success with scheduling a database migration and wanted to let you know how I did it in case you have a similar requirement. My requirement comprised of copying two databases that were 30 GB in size, from one server to another, during a time that I wouldn’t be at the office. Remote work was not possible. The Script Here’s the scheduled-migration.ps1 script that ultimately worked for me.

Another Batch of New Commands Now Available!

Chrissy LeMaire

dbatools is not only intended to be a great migration tool, but also a toolset to help DBAs follow best practices. Check out all the new commands in this batch, courtesy of Mike Fal, Constantine Kokkinos and Chrissy LeMaire. Best Practices Commands Ever read a really great article about how to do something properly but then kinda forgot and you have to revisit each time? Well, we’ve codified some of those practices for you, making them easy to both follow and remember.

New Best Practices Commands Now Available

Chrissy LeMaire

So many SQL Server and PowerShell pros have joined the dbatools team and we’re producing well designed PowerShell commands like mad! dbatools is not only intended to be a great migration tool, but also a toolset to help DBAs follow best practices. We like to think of these commands as fully automated Wizards that are executed from the command line instead of the GUI. Best Practices Commands Ever read a really great article about how to do something properly but then kinda forgot and you have to revisit each time?

← Previous

1 2 3 4 5

Page 5 of 5