In this month’s release, we gained 6 new contributors to the dbatools master repository for a grand total of of 26! This was likely the result of moving the repository to the new organization on GitHub called the SQL Server Community Collaborative, which makes it easier to participate in the dbatools project.
We fixed 15 bugs and added 9 new commands including one that migrates SQL Server Integration Services!
This command migrates Folders, SSIS projects, and environments from one SQL Server to another.
By default, all folders, projects, and environments are copied. The Project parameter can be specified to copy only one project, if desired.
The parameters get more granular from the Folder level i.e. specifying folder will only deploy projects/environments from within that folder.
We’re working towards this command being a wrapper for other new commands including Copy-SqlSsisFolder, Copy-SqlSsisProject and Copy-SqlSsisEnvironment.
This command searches all directories associated with SQL database files for database files that are not currently in use by the SQL Server instance.
By default, it looks for orphaned .mdf, .ldf and .ndf files in the root\data directory, the default data path, the default log path, the system paths and any directory in use by any attached directory.
By default outputs a small set of information around the Availability Group found on the server.
This command retrieves and compares the date/time for the last known good DBCC CHECKDB, as well as the creation date/time for the database.
This command displays processes associated with a spid, login, host, program or database.
This function returns agent jobs that active on the SQL Server intance when calling the command. The information is gathered the SMO JobServer.jobs and be returned either in detailed or standard format.
This command will help you set MaxDop configuration according to Microsoft recommendations.
When you switch a database into FULL recovery model, it will behave like a SIMPLE recovery model until a full backup is taken in order to begin a log backup chain. This command, inspired by Paul Randal’s post, will let you easily see if a database is in the ‘pseudo-Simple’ recovery model.
These are just general recommendations for SQL Server and are a good starting point for setting the “max degree of parallelism” option.
Some commands almost made it to this release, but didn’t.
Renames not just the database but the underlying files.
Gets the minimum, maximum and average throughput in Mb/sec for all or one database on a server for all time or filter by month, day or year.
This is already a pull request in the development repository! Just a bit more development is needed.
T-SQL based maintenance plans can’t safely access Windows file system to determine if a file has been properly archived. PowerShell makes it easy. This command will make it easier to clean up old, archived (and unarchived) backups.
Want to see more or work on a command yourself? We have approved command ideas on the dbatools Trello board. This board shows you what we’re working on and what we’re talking about. We’d love if you’d join us.
Some of these commands are in their infancy. Want to help make them better? Come join the coding party! We’re all hanging out on the SQL Server Community Slack in the #dbatools channel.