Pages

If dbatools has ever saved you time, either through our migration commands or easing SQL Server automation in general, please consider sponsoring one or more of us for a couple bucks a month. Sponsoring one or more of our developers through GitHub’s new Developer Sponsorship Program will help dbatools continue to live on, which ultimately means an easier, funner time at work for you as you relax while dbatools does all of the heavy-lifting.

Sponsorship

If dbatools has ever saved you time, either through our migration commands or easing SQL Server automation in general, please consider sponsoring one or more of us for a couple bucks a month. Sponsoring one or more of our developers through GitHub’s new Developer Sponsorship Program will help dbatools continue to live on, which ultimately means an easier, funner time at work for you as you relax while dbatools does all of the heavy-lifting.

Your First Pull Request

Here’s a quick tutorial on creating your first pull request. Fork the project, clone your fork, and configure the remotes: # Clone your fork of the repo into the current directory git clone https://github.com/<your-username>/dbatools.git # Navigate to the newly cloned directory cd dbatools # Assign the original repo to a remote called "upstream" git remote add upstream https://github.com/dataplat/dbatools.git If you cloned a while ago, get the latest changes from upstream: git checkout development git pull upstream development Create a new topic branch (off the main project development branch) to contain your feature, change, or fix: git checkout -b <topic-branch-name> Commit your changes in logical chunks.

Contact

Holler Thank you for your interest! It is best to write with questions or issues on our GitHub Repo. We are also on the SQL Server Community Slack in the channel #dbatools.

Guidelines

Here are a few things to keep in mind when programming for dbatools. Minimum Requirements One source of pride for this project is that it works on most systems. We at least try to make it work on SQL Server 2000, though sometimes it’s not possible. SQL Server 2005 and above usually works well. Also, remember that this module is intended for migrations and hence older systems, so PowerShell v3 is the base that we’ll be using to program.

Developing for dbatools

First thing is first, if you contribute a major amount, you’ll be added to the Major Contributors on the Team page 😀 Help Us Build an Amazing Toolset The types of commands we are looking for simplify whole tasks. As Microsoft continues its work on the PowerShell module for SQL Server, we’ll be here building commands for DBA Best Practices and common painful tasks. Benefits Help your fellow DBAs and yourself Build your resume Be an all-star DBA Ready to Join?

Developing for dbatools

First thing is first, if you contribute a major amount, you’ll be added to the Major Contributors on the Team page 😄 Help Us Build an Amazing Toolset The types of commands we are looking for simplify whole tasks. As Microsoft continues its work on the PowerShell module for SQL Server, we’ll be here building commands for DBA Best Practices and common painful tasks. Benefits Help your fellow DBAs and yourself Build your resume Be an all-star DBA Ready to Join?

#dbatools on Sqlcommunity.slack.com

Slack is a collaboration platform (okay, it’s kinda just an enhanced IRC ;)) It requires an invite, but you’re invited! Just enter in your email and this page will send you an email with the link. Ultimately, you’ll be joining us at sqlcommunity.slack.com in the #dbatools channel. To hang out, you can use the website itself, a desktop client or the mobile app. Once you have arrived, click CHANNELS then #dbatools

Slides / Videos

Presentation Materials Slide Deck (Filled With Comments) From “Simplifying SQL Server Migrations Using PowerShell” Slides Demo code Videos Migrate an Entire Instance In this video (sound coming later), I migrate a fully stocked instance to a rather empty one. Migration includes databases, logins, SQL Server agent, agent categories, alerts, audits, audit specifications, backup devices, central management servers, credentials, custom errors, database assemblies, database mail, data collector sets, endpoints, extended events, jobs, linked servers, operators, policy managements, proxy accounts, resource governor, server triggers, shared schedules, sp_configure and user objects in system databases.