Protecting production data in non-production environments
In this article, Grant Fritchey looks at the need to ‘shift left’ the database and associated database testing, while keeping sensitive data secure when it is outside the production...
Statistics in SQL: The Mann–Whitney U test
Phil Factor shows how to use the Mann-Whitney U test in SQL to to find out whether two samples come from the same distribution.
Improving Log Shipping
Today Steve Jones looks at possible ways to improve log shipping and asks for your input as well.
PowerShell Tool Time: Our First Toolbox
Learn how to begin assembling your functions and code into modules you can easily call from any session.
What is the biggest mistake you made in production?
When you have sysadmin access, you are bound to make a big mistake in production at some point in your career - in this post Tara Kizer looks back at what hers were.
Appreciating New Perspectives
Today Steve Jones talks about understanding and having empathy for other points of view.
Resolving could not open a connection to SQL Server errors
Have you ever gotten connectivity errors from SQL Server? Jugal Shah explains the common causes for these errors, and advises on the steps you can take to resolve them.
Database Development Made Easy?
Today Steve Jones has a few thoughts on the complexity and cumbersome nature of database development.
Automating the Synchronization of RDS SQL Server Agent Jobs in a Multi-AZ Environment
Although Azure is the obvious Cloud service to host SQL Server, Amazon Relational Database Service (RDS) for SQL Server is a good choice when your organisation uses AWS. RDS deals with maintenance and monitoring, and supports the use of PowerShell to automate routine tasks. What if a script needs to be triggered by an unscheduled event? Even in this case, RDS can be configured to run scripts to react when something like a failover happens. Laerte Junior shows how easy it is to set up Lambda functions and some PowerShell scripts to automatically synchronise agent jobs after a failover.
Fighting Evil in Your Code: Comments on Comments
One of the most glib generalisations you can make about development work is to say that code should be liberally commented, or conversely that it should never be commented. As always, the truth is more complicated. There are many different types of comment and some types are best treated firmly with the delete key, where others are to be cherished and maintained assiduously. Even though it is hard to find two developers who agree on the topic of commenting, Michael Sorens warily sketches out the issues and the battleground.
Blogs
How to Measure AI Value: A 6-Branch AI Maturity Model for Use Cases and Agents
Your AI is busy. But do you know what it's worth? Most companies can...
Speeding Up Patching – Beyond Patch Delivery
By Brian Kelley
I wear many hats in technology, and one of those is as a (cyber)security...
Monday Monitor Tips: Query Recommendations
By Steve Jones
We keep adding stuff to Redgate Monitor, and it’s easy to miss some of...
Forums
Azure SQL Hyperscale Unveiled
Comments posted to this topic are about the item Azure SQL Hyperscale Unveiled
What is the worst part about existing monitoring solutions?
Hi. What is the most difficult aspect of using monitoring software like idera, redgate,...
MiniMax m3 and SQL Server
Comments posted to this topic are about the item MiniMax m3 and SQL Server
Question of the Day
SQL Server Vector Support I
What are vectors in SQL Server 2025, as related to the new AI features?
See possible answers