Honestly, there is an alternative way to quickly use SSMS SQLCMD mode as a development environment, let us learn about it today.
SQL Server emergency? Email pinal@sqlauthority.com with URGENT in the subject line.
sqlcmd vs SSMS: How to Time the Same Loop Fairly
A sqlcmd vs SSMS timing is fair only when both tools run the same file. The clock must sit inside the script. This post times 10,000 inserts three ways with a log table, shows what changed and what didn’t, and lists the settings to match before you compare.
oStress vs SSMS: What Each Tool Is Built to Measure
oStress vs SSMS is not a race, because the tools measure different things. This post times 10,000 inserts in three ways with a clock inside the script, then shows how eight sessions finish the same work faster. It explains what a one-session loop really measures.
oStress Load Test: Run Many Sessions Against SQL Server
An oStress load test runs one query from many connections at once, so you can watch SQL Server under a crowd. This post explains the main switches and runs a small first test with five connections. It also builds the same test with sqlcmd workers, for machines without oStress.
What is Transactional Replication Supported Version Matrix? – Interview Question of the Week #274
Question: What is the Transactional Replication Supported Version Matrix?
The rules for the supported versions are pretty simple and clearly written.
Query Store On or Off for Every Database: Review First
To turn Query Store on or off for every database, you need one statement per database, because there is no server switch. This post builds a tested script that writes the statements, lets you read them and then runs them in one batch. It also covers READ_ONLY mode and the model database.
Query Store Status for Every Database in SQL Server
Query Store status for every database takes two queries, and the first is not enough. This post builds four demo databases, shows why the is_query_store_on flag hides frozen and read-only states, and runs one script that reads the real state of each database. It also shows what Query Store costs in memory.
SQL Server slow? Let's fix it together in about four hours.
In my Comprehensive Database Performance Health Check, you share your screen, I guide you, and we fix your biggest performance troublemakers. No passwords. No remote access.
You keep every script, and the know-how to fix it yourself next time.
Want your whole team to learn it?
My Practical Workshop has no PowerPoint, just live demos. My AI Enablement Workshop shows your team where AI saves hours, and where it quietly costs them.
Over 400 customers have worked with me this way, and not one shared a password. See all consulting options.