Blocking in SQL Server is normal behavior, but excessive blocking can lead to many complaints and is a symptom of poor performance. SQL Server contains a vast amount of information that can help when troubleshooting performance issues like blocking, but understanding and gathering that information when you need it is a lot of work. Darko Martinovic explains his solution for a custom blocking report.
The advantage of Setting the readable secondary as Read-Intent Only will allow the secondary server to serve the read-only workload only if the connection string of the application contains Application Intent=Readonly parameter.
Big Data hasn't been in the news, perhaps because more organizations are realizing they need the right data.
In this tip, Manvendra Singh will cover how to add another database to an existing Always On Availability Group.
SQL Server 2017 lets you solve parameter sniffing problems - Automatically!
This Friday Steve Jones wants you to look back and cringe a bit. Share with the rest of the community what a bad day was for you and see if it was really as bad as you think.
It's 15 years after the beginning of the century. Time to eliminate the security exposure of SQL logins, and implement integrated security. Active Directory Groups make this easy for the DBA.
In this tip, Edwin Sarmiento looks at how to create the Always On Availability Group with a listener name when using SQL Server on Linux.
Explore Batch Mode Memory Grant Feedback that was introduced in SQL Server 2017
Reading tutorials is fine. Shipping something is better. If you are trying to break...
By Steve Jones
We work hard at Redgate, though with a good work-life balance. One interesting observation...
By Arun Sirpal
Fourth in a series on Ai and databases. What Read-Only Advisory Actually Means A...
Comments posted to this topic are about the item Liability for AI Errors
Hello , I would like to run a stored procedure on a secondary replica...
Comments posted to this topic are about the item Pro SQL Server Internals
I run this command to start SQLCMD:
sqlcmd -S localhost -E -c "proceed"At the prompt, I type this (the 1> and 2> are prompts):
1> select @@version 2> goWhat happens? See possible answers