A blog post about writing blog posts
I recently wrote about how I teach, in response to a T-SQL Tuesday post from 2010. This is a continuation of that theme, suggested by my own editor. Thanks,...
2021-03-26 (first published: 2021-01-13)
186 reads
Randolph West
- Twitter: @_randolph_west
- Website: https://bornsql.ca/blog/
- LinkedIn: https://linkedin.com/in/rabryst/
What is a community advisory board anyway?
For those of us who have been involved in the Microsoft Data Platform community for a few years, the events of the last few months have been dramatic, culminating...
2021-03-24
22 reads
T-SQL Tuesday Retrospective #012: Why DBA skills are necessary
This is my ongoing series of answering T-SQL Tuesday posts far too late to be of any use. Click here if you want to read previous entries. Paul Randal...
2021-03-17
137 reads
T-SQL Tuesday Retrospective #011: Misconceptions
(If you would like to read the previous T-SQL Tuesday Retrospective entries, visit this link.) In October 2010, Sankar Reddy asked us which misconceptions we’ve been labouring under when...
2021-03-16 (first published: 2021-03-10)
309 reads
Which configuration changes in SQL Server require a restart?
SQL Server is a complex beast, with many configuration options that can range from recommended to completely avoided. Since the release of SQL Server 2016, several options that were...
2021-03-03
61 reads
Welcome to the Azure Data Community, empowered by Microsoft
After the Professional Association of SQL Server (PASS) unceremoniously closed down in January this year and its video library & brand names were bought by Red Gate Software Ltd, it...
2021-02-24
99 reads
Calgary Data User Group – 24 February 2021 at 5pm MST
This Wednesday, from 5pm to 7pm Mountain Standard Time, the Calgary Data User Group is presenting two sessions for your virtual attendance. 15 minutes: A lightning talk on Kubernetes...
2021-02-22
22 reads
Professionalism in the age of COVID-19
Some years ago, I wrote about what it means to be “professional” (and that it doesn’t mean having to wear a suit and tie). Recently a conversation broke out...
2021-02-10
169 reads
T-SQL Tuesday Retrospective #010: Indexes
(You can see previous T-SQL Tuesday retrospectives by visiting this link.) In September 2010, Michael J. Swart (blog | Twitter) invited us to talk about indexes. Indexes are strange...
2021-02-03
24 reads
T-SQL Tuesday Retrospective #009: Beach Time
(If you’d like to read my other T-SQL Tuesday Retrospective posts, click here.) In August 2010, Jason Brimhall (blog | Twitter) invited us to discuss preparing for vacations: “Write...
2021-01-27
13 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