PowerShell with SQL Statement Data Gathering
summary
PowerShell connects directly to the database with invoke-sqlcmd and a custom OpsVerification module instead of fragile web scraping or RPA, runs as a scheduled task under a service account, and emails results into PagerDuty email-to-push; the concrete rule is a 150-record threshold (151+ trips an alert) and queries also flag records older than 24 hours. A test MySQL demo and runs on Windows PowerShell 5.1 and PowerShell 7.3 show the modules and scheduled process actually work.
AI-written summary · about
chapters (6)
- 0:00Monitoring ATM transactions
- 4:10Automate SQL data gathering
- 13:49SQL Server module
- 27:53Verification module demo
- 35:14PowerShell automation best practices
- 38:15Q&A
related talks
44mContinuously deploying SQL code using Powershell
49mMonitoring Using PowerShell
36mSQL Server Configuration with dbatools & dbachecks
46mAn IT Operations Approach to Observability
44mMy romantic relation with Powershell generally and DBATools especially
53mUnlocking the Power of the SQL Server PowerShell Module
01h 47mBuilding PowerShell Applications that Operate on a Planetary Scale
47mTrending and Reporting