Had a need to look into a Trello board's activity and thought I would blog the first of some "recipes" I am coming up with.
To start it off, I wrote some trivial functions to format Trello URLs (as they appear today) to return the JSON representation of the board, and return some basic information about the activity that recently occurred.
This Gist is not a full fledged module as of yet, just a bag of functions and a little extra code. On line 54 I define a hash of boards and then break out the activity and cards updated in the last 10 days.
More than anything this code had me diving deeper with JSON, spending some time figuring out what I could do with PowerShell Format Expressions, and a bit of checking/capturing the implicit type conversions PowerShell loves to throw at me.
I know there is more to do here and I could be significantly more terse, could remove the hash table, and the naming might not work if they provide a url without the pretty printing, so I could definitely add more sanity checking in the Format-TrelloUriToJson function.
For my second TSQL Tuesday post, I wanted to introduce a nifty feature in the dbatools lineup called Restore-SQLBackupFromDirectory, which used Ola Hallengren’s scripts as a baseline to restore a server from a backup folder, un/fortunately I came across a newer command that Stuart Moore engineered (Restore-DBABackup) which made it entirely redundant, expect his post coming very soon.
Since there was a bit of a last minute pivot, we are going to do a whirlwind tour of two new PowerShell commands that just hit the lineup regarding database backups, Get and Remove DbaDatabaseSnapshot.
These along with an additional function coming soon (New-DbaDatabaseSnapshot) are going to make it super simple to create, list, and remove database snapshots on your SQL Server instance.
Drops snapshots from your SQL Server.
This has an additional unique parameter of -Snapshots, which allows you to filter on exact snapshot name instead of using a base database name (in the case of multiple snapshots you want to remove.)
Common Parameter Reference
As with many commands in the dbatools lineup there are several common parameters:
SqlServer – Indicates what server you would like to operate on.
Credential – Allows you to include an overriding SQL Login credential (PowerShell object),
Databases – Operates as an inclusion filter for database names.
Exclude – Operates as an exclusion filter for database names.
Hopefully after reading today you have two commands ready to help you manage your database snapshots, and I have whet your appetite for the upcoming restore and snapshot commands coming soon!
If you don’t see the filtering/parameter populating from tab completion, this indicates an issue connecting to your SQL Server.
Both of these commands were written recently by one of the newest contributors to the project, niphlod, great job!
If you want to learn more about dbatools (free PowerShell module with nearly 100 SQL Server administration, best practice and migration commands included) checkout https://dbatools.io, we have a growing team and we want contributions from busy SQLDBAs like yourself.
If you are unsure where to start or just want to join the growing communtity, you can find us on the SQL Community Slack feel free to send me a message if you need some help!
I was performing some final minor fixes on Find-DbaOrphanFile (helps cleanup files unattached to your server in default directories and additional folders you specify) and ran into an issue parsing the filenames returned.
In the process of changing the code to fix some other issues, IO.Path.GetFileName was added to properly enumerate the paths returned, and when testing it in the dbatools lab (Thanks @ctrlb!!!) it was failing on SQL 2000.
After a few attempts at parsing out slashes and various .trim commands I broke out the command in the PowerShell debugger (which I will detail in another post) and I was thinking of converting everything to numeric representations to double check their character values, but there was no need, the console had done the work for me:
The Find-DbaOrphanedFile (now with an additonal ltrim and rtrim in SQL instead) command now works!
As a little aside, why even test SQL 2000?
One of the first things dbatools strove to do was migrate effectively between different versions of SQL Server, and we want to support SQL 2000 up to the most recent SQL version if possible, we do this because we want to offer the cool tools as far back as possible, we know that many people will be using old versions for many years to come.
It hurts sometimes and some of the code can get a bit hacky, but I think most of SQL 2000’s differences are interesting and long term forcing ourselves to manage different versions of SQL Server is reducing the into adding new and fundamentally different databases, such as all the interesting things that are coming with vNext.
And as always, this is one of the many dangers of using undocumented stored procedures :)
@sqlbek (Andy Yun) posted a challenge for T-SQL Tuesday 84, where he encouraged people thinking about becoming a speaker to write about their experience giving their first talk, a topic they wanted to present on in the future, or even on starting the road to creating their blog and establishing themselves in the SQL space.
I wanted to flesh out an idea I had for a my first talk that would last under 15 minutes or so.
I was thinking of targeting this at a user group (hopefully with a few production DBAs where are interested in learning more about PowerShell) to foment some excitement for and share my experience with dbatools.io
who (am I)
I am a production DBA who focuses on performance tuning for a few thousand users.
I haven’t written anything you’ve read (yet).
I have been poking around with PowerShell for more than a year, before this experience I had written only a few small things that made it to production. Definitely beginner skill level.
have you ever wanted to…
Migrate your SQL Server painlessly?
Double check that you have the best practices configuration for component or feature X which you are not an expert in?
Centralize the knowledge you find scattered around on various blogs and SQL wizard cabals?
what (do I want to tell you)
I am here to introduce your to dbatools, an open source project, to talk about my experience going from pure production DBA to PowerShell convert, and to talk to you about how augmenting your skills with some of these commands can mean very little effort expended for a significant payoff.
As a production DBA, I am responsible for a host of things, and I am often a little buried under the mountain of work that piles up, along with every day work, among other things I am responsible for:
Reporting on and managing configuration drift
My environment is growing rapidly, so I started looking for tools that I could use to help me do my job in a way that didn’t leave me in a cold sweat at night.
dbatools was created help busy DBAs do their jobs, hopefully encoding best practices and reducing the cargo culting in the SQL Server community.
While dbatools was originally designed to migrate your SQL Server instance’s objects from one server to another it is currently expanding into a set of commands (cmdlet reference ) that I think many of my peers in the SQL Server would find very useful.
I first heard about dbatools in the SQL Community Slack and loved the demo on the front page showing how simple a migration is:
I was a bit gobsmacked as I had just finished my own instance migration, and it certainly took a significant amount of time and effort compared to this painless invoking of this cmdlet.
A bit of hanging around and even though I felt unfamiliar with PowerShell development, I was was roped into writing my own cmdlet .
To be frank, looking back at my first draft is painful.
I was worried about my code quality given my experience, and so I asked for some feedback from the head of the project Chrissy LeMaire.
What I got back was almost unrecognizable as my code, and it was one of the first times I was able to see my feral PowerShell (that did the job, badly) turned into something that you could consider idiomatic code.
I learned more in that code review than I had in the previous year of starts and stops in PowerShell land and spent the next week picking it apart and asking questions to cement my knowledge.
In one week I had expanded my PowerShell knowledge by at least 20 times, and felt way more comfortable in working with the team to build some command or troubleshoot an issue!
In the end I had a fairly robust cmdlet and with minor bug fixes it made it into the release!
I was super happy to have something published in an open source project, but even more, I was happy to have found a series of mentors who wanted to help me build my skills as a PowerShell and database developer.
A few pull requests and a few months later I am confident in my PowerShell abilities to figure stuff out, work through problems, and help newbies through their first steps to contributing to dbatools.
The small scope of PowerShell I have been able to learn and utilize has made things which at one time seemed daunting now seem possible, and even easy.
Now I want to help you make my story your story, contribute to dbatools.
Any time you want to.
dbatools is a community that lives in the #dbatools channel in the SQL Community Slack.
Any time day or night people are chatting, working on code, listening on feedback to improve the tools, and answering questions for people looking for help using it.
Come and express interest in contributing, we will help you through the rest!
Been a few days of learning since I last wrote one of these, but I have come back to the automatic variables page on the PowerShell documentation enough times that I think I should just blog the important parts for myself.
$? – TRUE/FALSE if the last thing you did succeeded.
$_ – Something everyone uses in posh, current pipeline object.
$Args – all the undeclared params passed to a function, try to avoid.
$Error – the array of error objects that represent a stack of the most recent errors. use $Errors0 to get the most recent error.
$Home – full path of home directory of the current user.
$Host – methods to access information about the host we are running the PowerShell command on.
$Matches – used with the -(not)match operators, is populated with a hash table of the matched values.
$MyInvocation – name, params, values, and information about the current command. Super useful for weird introspection.
$OFS – Output File Separator, allows you to set the default file separator for array operations. Generally better to set variables to send to split, this can have downstream effects if you dont change it back.
$PID – PID of the process hosting the current PowerShell process.
$PSBoundParameters – Nice shortcut to refer to all the params to another script or function.
$PsCmdlet – mostly used in advanced functions to access the current running cmdlet’s properties.
$PSCommandPath – full path and file name of the script being run.
$PSDebugContext – if $null, debugger is not running.
$PsHome – path to PowerShell install dir.
$PSScriptRoot – directory where script is being run from, avoid if you want to support ps2.
$PsVersionTable – returns read only hash table about the current ps session.
$Pwd – a path object representing the current directory.
$StackTrace – shortcut for the stack trace of the most recent error.
$This – refers to an object that is being extended in a script property or method.
$true/$false/$null – use boolean login on all of these, nothing new here.