If you work in a secure environment or your computers cannot access the Internet for any reason, you can still install dbatools with ease by downloading the zip from a workstation that does have Internet access 🎉 And now that our module is digitally signed, you can keep your Execution Policy set to AllSigned, too.
There are essentially 3 ways to get the zip of our module
From PowerShell Gallery using Save-Module From PowerShell Gallery by downloading from powershellgallery.
My favorite vacation ever was the time I visited Steve Jones’ wardrobe. It bore a striking resemblance to Maui and even came with complimentary piña coladas.
The year was 2009. The sun was out, Colbie Caillat was on the radio and I hadn’t mastered PowerShell yet, so I was left feeling frantic about the health of my SQL Server estate.
Now, though, I’ve got dbatools which allows me to quickly check the things that concern me most.
Recently, Constantine, Rob, Aaron, and I got together to record a podcast for SQL Data Partners with Steve Stedman and Carlos L Chacon. We talked mostly dbatools, the community, open source projects and then I answered some SQL Family questions.
Today, the SQL Data Partners team released the podcast, along with a corresponding transcript.
Spoiler Alert: I know you’re all wondering what my superhero power would be, so here’s my answer 😊
So, there’s a World Backup Day, but what about World Restore Day? We’ve all been told over and over, backups are useless if they can’t be restored and verified. Grant Fritchey has even yelled it at us a couple times.
Using dbatools to Automate Tests dbatools makes it crazy easy to automate your backup testing, as demonstrated by Sander Stad, Rob Sewell and Anthony Nocentino. It even works on Linux!
So, we’ve made the first step to 1.0 - we’ve stopped accepting Pull Requests that add new commands. It breaks my heart the most, but every moment that we spend vetting a new command is a moment we can’t spend bug fixing and we really need to focus on standardization and bug fixes.
Our pull request queue is currently filled with new commands that we still need to review, along with a couple bug fixes.
Recently, I presented to the Philadelphia PowerShell User Group about Contributing to Open Source PowerShell projects using GitHub Desktop. I chose this topic because a number of people have asked for step-by-step instructions on how to work with GitHub.
I love the command line, but with Git? I think it’s important to get the concepts down first and the Desktop version makes that a lot easier to contribute to projects like dbatools, dbareports and even PowerShell itself.
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.
When I first began working on dbatools, I was aware of the suggestion to use a distinct prefix in PowerShell, but chose to use Sql for its universal recognition. That will soon change.
PowerShell Prefixes Prefixes are the things that start the noun. SQL Server uses Sql, Active Directory uses AD, SharePoint uses SP, PowerShell uses PS and Lync uses Cs. You can see, even with two letter prefixes, that there is no true case consistency.
When I first began working on dbatools, I was aware of the suggestion to use a distinct prefix in PowerShell, but chose to use Sql for its universal recognition. That will soon change.
PowerShell Prefixes Prefixes are the things that start the noun. SQL Server uses Sql, Active Directory uses AD, SharePoint uses SP, PowerShell uses PS and Lync uses Cs. You can see, even with two letter prefixes, that there is no true case consistency.
dbatools