SQL Saturday Comes to Pensacola
SQL Saturday comes to Pensacola, June 6, 2009. Read on to get more information and sign up for a one day, free training event.
2009-02-23
330 reads
SQLSaturday
Notes from SQLSaturday #10 in Tampa
SQLSaturday #10 was held January 24, 2008 in Tampa at the Kforce Building. Attendance was about 175, down slightly from the year before. Overall the event turned out well; 36 sessions, everyone got fed, no major logistical challenges.
2009-01-29
662 reads
SQLSaturday #10 - Tampa 2009
Looking for free SQL Server training?
Join over 250 SQL Server professionals in Tampa on January 24th, 2009 for SQL Saturday #10. Featuring 6 tracks and more than 36 SQL Server presentations, it's the biggest and best free SQL event available. Visit www.sqlsaturday.com to see event details and to register.
2008-12-15
1,196 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