We are so super excited to announce that after 5 long years, dbatools 1.0 is publicly available!
Our team had some lofty goals and met a vast majority of them 🏅. In the end, my personal goal for dbatools 1.0 was to have a tool that is not only useful and fun to use but trusted and stable as well. Mission accomplished: over the years, hundreds of thousands of people have used dbatools and dbatools is even recommended by Microsoft.
We recently released a VS Code extension that lets you highlight terms and search dbatools.io, Microsoft Docs, Google, StackOverflow, DuckDuckGo, Technet or Thwack right from your code! It’s called search from code and you can find it in the Extension Marketplace.
Options and Settings By default, only Google, docs and dbatools are enabled but you can configure whichever providers you’d like in VS Code Settings.
At first, I was just messing around to see what it took to create a VS Code extension, but then I realized that I was actually using it and decided to share.
We’ve made even more progress in the past week! Here are some highlights of 0.9.520.
Non-Breaking Changes Aliases have been added for the changes, so these are not breaking changes:
Mismatched Copy commands have been renamed to match their corresponding Get command names (ie. Copy-DbaCentralManagementServer is now Copy-DbaCmsRegServer). Most parameters named Password have been changed to SecurePassword. They’ve always been a SecureString data type but this makes that clear. The parameters ExcludeAllSystemDb and ExcludeAllUserDb have been changed to ExcludeSystem and ExcludeUser, respectively.
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.
Last night’s #PSPowerHour made me realize I should highlight a few awesome projects I’ve come across recently.
PSDatabaseClone PSDatabaseClone was created by Sander Stad.
PSDatabaseClone is a PowerShell module for creating SQL Server database images and clones. It enables administrator to supply environments with database copies that are a fraction of the original size.
It is well-documented and open-source.
dbops dbops was created by Kirill Kravtsov.
dbops is a Powershell module that provides Continuous Integration/Continuous Deployment capabilities for SQL database deployments.
Last night was the premiere of #PSPowerHour! It featured great speakers and a lot of dbatools content.
What is PSPowerHour? Created by Michael T Lombardi and Warren F, PSPowerHour is “like a virtual User Group, with a lightning-demo format, and room for non-PowerShell-specific content. Eight community members will give a demo each PowerHour.”
Sessions are proposed and organized on GitHub, which is really cool. Both new and seasoned speakers are invited to propose topics 🙌
Congrats to our teammate Rob Sewell! Rob was invited by PASS to present about PowerShell at PASS Summit 2018 on Tuesday, November 6 2018.
In his day-long session, Rob will talk about a variety of super interesting subjects including: dbachecks, PowerShell module-making, GitHub, VSTS, and dbatools. Rob is a vibrant, knowledgeable speaker and I can’t recommend this precon enough! I learn a ton every time that Rob and I present together.
Azure Data Studio (formerly SQL Server Operations Studio) by Microsoft is like SSMS for ops, all open source and published on GitHub! They updated their wiki’s Performance page, addressing why SQL Operations Studio starts up slowly. Their startup stats are pretty cool!
This screenshot reminded me that I should write about our own import time stats.
Confession You may remember years ago when I expressed how upset I was about SQLPS, SqlServer’s predecessor, taking so long to import.
Years ago, I wrote Watch-DbaDbLogin which keeps an inventory of accounts, hosts and programs that log into a SQL Server. It was pretty crude, but helped immensely during my migration, as this inventory ensured that my documentation was in order and no unexpected downtime would occur.
I found that about 80-90% of logins/applications were covered within 48-hours, but two months of data gave me total confidence.
I always wanted to update the command, though I’m not sure Watch-DbaDbLogin is still within the scope of the module.
Last week I performed a server migration from SQL Server 2014 to SQL Server 2016 using dbatools. A lot of work is done up front to prepare and plan for these migrations to have the least impact on our customers. So I always do my best to improve the process each time we do it.
Backstory This is the second product server we have migrated to SQL 2016. The first migration had automation to a certain point.