Query Store - Part 4 - Find the plans and queries forced by Query Store
As most of you know, one of the most fundamental uses of query store is to force query plans. Unlike...
2016-12-08
1,077 reads
SQL and SQL Only
Data Channel - Interview 01 - Andreas Wolter on Columnstore
Dear all,
Welcome to the first ever interview of DataChannel. I am honored to have Mr.Andreas Wolter, a German MVP, MCM, MCSM...
2016-12-03
725 reads
SQL Server 2016 SP1 – Rocking RELEASE!!!
Last week, I did a presentation titled "SQL Server 2016 SP1 – Rocking RELEASE!!!" to Singapore SQL User Group. The Presentation was...
2016-11-29
850 reads
Data Channel - Launch
Dear All,
I am starting a YouTube channel for SQL Server and Microsoft Data Platform Technologies called "Data Channel". What this...
2016-11-26
413 reads
SQL Server 2016 - SQL Service Doesn't Start after GDR Security update
Recently, after an security fix GDR (https://support.microsoft.com/en-us/kb/3194716) on SQL Server 2016 RTM, SQL Service refused to start. Though, the patch...
2016-11-20
1,182 reads
SQL Server 2016 SP1 Release - Thoughts and Comments!!!
SQL Server 2016 SP1 has released last night and most of the features that were previously part of enterprise edition...
2016-11-17
722 reads
Residual Predicate and "Number of Rows Read" in Execution Plans
What is Residual Predicate?
Lets say one gets a query to fine tune. While checking the execution plan, if there is...
2016-11-17 (first published: 2016-11-13)
4,623 reads
SQL Server 2016 - “Number of Rows Read” on Execution plan
One of the coolest things to release with SQL Server 2016 was “Number of Rows Read” information in execution plan....
2016-11-10
829 reads
Query Store - Part 3 - How it works?
Query Store collects 2 important kinds of data. They are
1) Compile time statistics - Query Plan, Estimated Costs, Estimated number of...
2016-11-06
806 reads
Folders to Check for errors in SQL Patching or Installation
Recently, while applying SQL Server 2012 Service Pack 3, encountered the following error and SQL Patch failed to upgrade.
"The patch...
2016-11-04
6,722 reads
Blogs
Flyway Tips: AI Deployment Script Descriptions
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
A New Word: Fawtle
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
Post-quantum key exchange – Insurance policy for your packets
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
Forums
Where Your Value Separates You from Others
Comments posted to this topic are about the item Where Your Value Separates You...
Fixing the Error
Comments posted to this topic are about the item Fixing the Error
T-SQL in SQL Server 2025: Encoding Functions
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
Question of the Day
Fixing the Error
On SQL Server 2025, I have a database that has this collation: SQL_Latin1_General_CP1_CI_AS. I decide I want to run this code:
SELECT UNISTR('*3041*308A*304C*3068 and good night', '*') AS 'A Classic';
I get this error:Msg 9844, Level 16, State 4, Line 24 The char/varchar input type uses an unsupported collation. Only a UTF8 collation is supported with char/varchar input type in UNISTR function.What is the easiest way to fix this error? See possible answers