Wait? Is this oh-my-posh running natively inside
Claude Code? Happy holidays everyone!
26.12.2025 11:24
👍 20
🔁 4
💬 0
📌 0
Wait? Is this oh-my-posh running natively inside
Claude Code? Happy holidays everyone!
We've even added a new command! Export-DbaCsv makes it easy to export CSV data from SQL Server. Includes fast CSV exports with GZip/Deflate/Brotli/ZLib compression, custom delimiters, quoting, date formats & encodings. Great for ETL, reporting, archiving, and moving big SQL Server datasets.
Of course, we've updated Import-DbaCsv to use this new library and no longer have a third-party dependency on Lumenworks. We also added functionality requested by our users (and Lumenworks users!) over the past 10 years such as compression and alternative delimiters.
We've just released a new CSV library for C#. If you're importing CSVs to SQL Server, it's 6x faster than LumenWorks with native IDataReader, built-in compression and progress reporting! Shoutout to Claude Code for making this possible by bringing efficient, secure C# development to PowerShell devs.
If it's a code problem, dbatools.io/issues. For live feedback/help, dbatools.io/slack -- join the #dbatools channel and there's a bunch of admins and users who can help 💙
😉
The screenshot shows the "dbatools Commands" page from the dbatools website, listing PowerShell commands for SQL Server. The interface includes a search bar, filterable categories on the left, and a grid of command cards in the center. Visible commands include “Copy-DbaLogin,” “Invoke-DbaQuery,” and “Restore-DbaDatabase,” each with a short description, a yellow star icon indicating popularity, and category tags like “Migration” or “Backup & Restore.” The site header includes links for Getting Started, Commands, Blog, Book, Team, GitHub, and Builds, with an “Install” button and dark mode toggle.
Look at that commands page featuring our nearly 700 commands 😍 So useful now and easy to navigate.
SQL Server Build Reference page from dbatools.io showing a dark-themed interface with filter buttons by version (e.g. SQL Server 2022, 2019, 2017) and by attributes (e.g. Service Packs Only, Cumulative Updates Only). Below is a searchable, exportable table listing SQL Server build data including version numbers, names, service pack (SP) and cumulative update (CU) info, end-of-support dates, and KB article links; top entries include version 16.0.4222, 16.0.4215, and 16.0.4212 with support ending 2033-01-11.
We even migrated the #SQLServer Builds Reference and made it an integrated part of the rest of the site dbatools.io/builds We've got Dark Mode now, too 🖤
Our website recently got an upgrade! It was initially built on WordPress in 2016 then after several hacks, was exported to HTML and put on @github.com's Pages in 2020. Now, it's been redesigned using Hugo and Claude Code. Let us know what you think!
Oh, awesome! For the next 5 hours, you can get a month free of Claude! #DevOps people, add it to your @github.com repo or use it at the CLI -- either way is incredible. I just updated my whole blog with it.
A console with the writing: **SQLDBAWithABeard's Pester Contributions – Deep Dive:** **The Foundation: November 23, 2016 – A Historic Day** SQLDBAWithABeard made 83 commits in a single day (November 23, 2016), fundamentally transforming dbatools' quality standards. This was just 6 months after June Blender added the first test file. **1. CI/CD Infrastructure Setup** Created the complete testing infrastructure: * tests/appveyor.pester.ps1 – A sophisticated test runner that: * Supports multiple PowerShell versions (v2+) * Serializes XML results for AppVeyor consumption * Uploads test results to AppVeyor's test page via API * Aggregates results from multiple PowerShell version test runs * Fails builds on test failures with detailed failure summaries * AppVeyor CI Integration – Set up continuous integration that: * Runs tests on native PS version and PS 3.0 * Installs Pester and PSScriptAnalyzer automatically * Collects and uploads test results * Added skip commit support for readme updates
A console that says: **2. Test-Driven Documentation Standards** Created tests/dbatools.Tests.ps1 – A comprehensive module manifest test that validates: * Module name, root module, GUID, version * Author and company information * PowerShell version requirements * Required assemblies * Critically: All exported functions match actual function files This test ensured the module manifest stayed in sync with actual functions. **3. The Great Documentation Cleanup (Nov 23, 2016)** After establishing the test infrastructure, he discovered widespread documentation gaps. His response: 83 commits in one day adding parameter help to pass tests across the entire codebase: * Added help for Force, WhatIf, Confirm parameters (ShouldProcess support) * Added SqlCredential, Detailed, OutputFile, Collection parameter help * Fixed function headers to match Pester requirements
One of my favorite things to use AI for is repo storytelling. Claude Code is SO good at using gh, git and its own tools to understand changes to @dbatools.io's repo and tell a story. Here, I asked it to detail @sqldbawithbeard.bsky.social's Pester contributions for my upcoming session at @psconf.eu
Screenshot of the PowerShell Gallery page for the dbatools module version 2.5.5, showing a large red arrow pointing to the total download count of 7,001,571, highlighting a milestone achievement; the page also displays 15,846 downloads for this version, the last published date of August 5, 2025, and an example PowerShell command to install the module.
SEVEN MILLION+ downloads on the PowerShell Gallery! Thanks to everyone who helped make this happen 🤗
If you build software, you're based in the US or Canada, and your organization has been around for at least 3 years, check out Azure Trusted Signing.
It costs $9.99/mo, which after 3 years, costs about the same as a 3-year DigiCert — all without the antiquated ID verification.
A PowerShell Core terminal displays detailed information about an X.509 certificate, showing fields like NotAfter (8/8/2025), NotBefore (8/5/2025), SerialNumber, Thumbprint, and Issuer. Two red arrows highlight the Issuer as "CN=Microsoft ID Verified CS AOC CA 02" and the Subject as "CN=dbatools, O=dbatools, L=Vienna, S=Virginia, C=US." The background includes a stylized purple-and-cyan avatar graphic in the lower-right corner, suggesting a personalized or themed terminal setup.
But how cool is it to have your software signed by @microsoft.com?
Also, check out that NotAfter and NotBefore, so short!
Or you can stay with version 2.5.1. That signature will be valid pretty much until the end of time.
Oh and going back to Install-Module, if you switch to Install-PSResource, that bypasses the SkipPublisherCheck requirement.
```
Install-Module Microsoft.PowerShell.PSResourceGet
```
Not up for dealing with daily cert rotation? You can set your execution policy to Bypass or Unrestricted.
If this sounds concerning to you, the post below should provide you with reassurance. Also, most if not all of us on the dev team set our Execution Policies to Bypass or Unrestricted if we can.
In PowerShell 7, we're looking forward to built-in support, hopefully coming soon. Shoutout to @jborean.bsky.social !
For users with strict ExecutionPolicies, we have a workaround for the daily cert rotation in Windows PowerShell.
Add this Import-Dbatools function to your profile to auto-trust certs:
A Windows Certificate Manager window shows the "Trusted Publishers" certificate store under "Certificates - Current User." The selected certificate is issued to "dbatools" and issued by "Microsoft ID Verified CS AOC CA 02," with an expiration date of August 8, 2025. Other listed certificates include several issued to "Microsoft Corporation" by "Microsoft Code Signing PCA 2011," mostly for Microsoft Publisher and code signing purposes, with varied expiration dates. The view indicates 10 total certificates in this store.
Our cert now shows Microsoft ID Verified as the issuer. Identity validation took just 30 minutes vs DigiCert's 2+ months.
Azure Trusted Signing provides instant reputation tied to our verified identity & not to a specific cert like the old way. Should finally solve years of false positives.
Upgrading from older versions? You'll need this ONE time:
```
Install-Module dbatools -Force -SkipPublisherCheck
```
After that initial transition, you won't need SkipPublisherCheck again since our cert keeps the same subject and root CA for version 2.5.5+ onward.
🎉 Big news! dbatools is moving to Azure Trusted Signing, which provides base reputation on Windows SmartScreen. No more antivirus false positives.
The catch? If you use strict ExecutionPolicies, you'll need to trust our cert after each update (it rotates daily). But we've got automation scripts.
I wrote a new post about a specific parameter on Backup-DbaDatabase that I didn't know existed.
The @dbatools.io module always amazes me, even though I use it everyday!
jesspomfret.com/dbatools-bac...
😌 oh good. Happy that was the issue after getting that notification!
Getting #SQLServer Version using @dbatools.io
#SqlBlog #PowerShell
nocolumnname.blog/2025/03/06/g...
Blog post from the past:
I which I demo creating and managing aliases via @dbatools.io, cliconfig, SQL Server Configuration Manager, and registry keys.
#sqlserver #sqldba #microsoftsqlserver #mssqlserver #mssql #mssqldba #powershell
vladdba.com/2023/09/29/c...
⚠️ Attention #HHPSUG #PowerShell people ⚠️
Our Hamburg PowerShell User Group today was hit by flu season and we have to move it to next week.
📆New date & time: 29.01.25 19:00 CET
Hope to see you all then.
www.meetup.com/hamburg-powe...
CC @funbucket.dev
Fantastic walk through of using @dbatools.io with PowerShell Universal. Jess provides step-by-step examples of pulling data back in APIs and building out an app to display database in tables. She even gets into the server-side paging. Worth a watch!
I’m getting so many ideas from this. And so little time.
So very cool. #dbatools & #PowerShellUniversal creating a dashboard enabling users to backup their databases and showing the current status. I also love that Jess explains some of the development process so that even if you're not a PowerShell expert you can still learn the steps to do this yourself
Put together a little video on using #PowerShellUniversal with @dbatools.io to create a cool dashboard!
What do you think? What should I add? (especially to the home page 🤣)
www.youtube.com/watch?v=DKD1...