Disabling SQL Server Optimizer Rules with QUERYRULEOFF
Daniel Farina shows how to disable the optimizer rules by using QUERYRULEOFF, an undocumented hint.
Daniel Farina shows how to disable the optimizer rules by using QUERYRULEOFF, an undocumented hint.
In a couple of days, Microsoft is holding Data Driven, an event that will highlight SQL Server 2016.
It sometimes pays to go back and look at what you think you already know about SQL. Joe Celko gives a quick revision of the GROUP BY and HAVING clauses in SQL that are the bedrock of any sort of analysis of data, and comes up with some nuggets that may not be entirely obvious.
Changing Database Collation Through Primary keys, Foreign Keys, Default and Check Constraints and more.
SMO gives every appearance of being a great example of over-reliance on automated testing at the expense of manual exploratory testing.
Hear from Microsoft engineering experts on the latest features in SQL Server 2016 before the live event. Learn about new business intelligence capabilities like built-in mobile BI, fully integrated advanced analytics, security innovations, mission critical in-memory performance and new hybrid cloud solutions.
Aaron Bertrand (@AaronBertrand) revisits the impact that eliminating DONE_IN_PROC messages using SET NOCOUNT ON may or may not have on query performance
Learn about how to build value driven analytics with SQL Server and R.
Today we have a guest editorial from Andy Warren that examines the costs of family at work.
By Steve Jones
A customer was trying to compare two tables and capture a state as a...
By Zikato
When I'm looking at a query, I bet it's bad if I see... a...
By Steve Jones
This month is a milestone for T-SQL Tuesday. It’s number 200, which doesn’t sound...
Comments posted to this topic are about the item A Quick Second Opinion
Comments posted to this topic are about the item Five Intelligent Query Processing Features...
Comments posted to this topic are about the item Checking the Error Log I
On my SQL Server 2025, I want to search the error log from my T-SQL code for potential issues and then inform an administrator. What is the current way to easily query the error log?
See possible answers