We’ll takes your output to the next level by sending your data to your own SQL instance. Whether it’s inventory or whatever your lead wants you to gather, sending your data to a functioning SQL instance will save you in the long run. We’ll create a basic tool that does just that saving you time & $

This session focus’ on moving admins away from capturing their data to CSV files or even simple text files…never to be found again. This could be a first step for a sysadmin getting comfortable with SQL while slowly graduating to the DBATools module for next level control. Leveraging a Docker SQL container, we’ll walk through the process of converting those standard “get-pcinfo.ps1” scripts to send data to their own SQL instance using PowerShell and creating some nice reporting using SQL Server Reporting Services.

Technical Requirements.

Demo will be 95% local. Considering an Azure component which will be recorded for a backup

The Why

I am by no means a SQL DBA ninja, however, I am spending a lot of my time developing coursework for Pluralsight which involves SQL migrations to Azure and have developed a fondness for the variety of things beyond CSV or text files. I think this is a topic that is always relevant and some folks may be afraid to take a look at their output differently. It also may tear down some of the imposter syndrome of “I’m not a DBA” and perhaps open up a whole new can of worms and graduate to using the DBATools module.