Who Changed the Schema? Find Out in SQL Server
See who changed the schema in SQL Server: the exact statement, login, host and application, captured by a DDL trigger you switch on per database.
See who changed the schema in SQL Server: the exact statement, login, host and application, captured by a DDL trigger you switch on per database.
We’re excited to announce that Database Health Monitor Version 4 is now available! Version 4 represents one of the biggest updates to Database Health Monitor since its original release. While the most obvious change is the completely redesigned interface, this release goes far beyond a visual refresh. We’ve rebuilt and improved nearly every part of the application to make it easier to understand what is happening inside your SQL Server environment and to provide more useful information when something needs …
Database Health Monitor Version 4 Has Been Released Read more →
See which SQL Server deadlock objects collide with each other, on what index, under what lock mode, and which one loses every time.
See who is connected to SQL Server right now, colored by state, so you can tell a connection leak from normal pooling before resizing anything.
Learn what signal wait time means in SQL Server wait statistics, why it signals CPU pressure, and how to read it before blaming the disk.
See which SQL Server trace flags on an instance are still doing anything on the current build, and which ones vanish at the next restart.
Find SQL Server unused indexes with sys.dm_db_index_usage_stats, see the write cost of keeping them, and get a verdict on every row.
When querying data in SQL Server, selecting the right join type can dramatically shape both the results and efficiency of your queries. Full Joins and Cross Joins stand out as two options that frequently lead to mix-ups, given how differently they handle data from multiple tables. A Full Join pulls every record from both tables involved, inserting NULLs wherever no match exists on the join condition. By contrast, a Cross Join creates every possible pairing of rows between the tables, …
SQL Server Full Join vs Cross Join: Key Differences Explained Read more →
See SQL Server historic reporting in one place: plan cache hit ratio, page life expectancy, CPU, deadlocks, and file growth, trended together.
In the wise words of Benjamin Franklin, “If You Fail to Plan, You Are Planning to Fail.” This timeless adage holds particular relevance when it comes to safeguarding your SQL Server databases. A failure to adequately prepare for data loss scenarios—be it due to hardware malfunctions, data corruption, or increasingly prevalent ransomware attacks—can have devastating consequences for your business. The Common Problem: Lack of Preparedness Despite the rising risks, it’s shocking how often we encounter businesses that are inadequately prepared …
We are ready to help. Steve and the team at Stedman Solutions are here to help with your SQL Server needs. Get help today by contacting Stedman Solutions through the free 30 minute consultation form.
Contact Info for
Stedman Solutions, LLC.
PO Box 3175, Ferndale WA 98248,
Phone: (360)610-7833
Our Privacy Policy