Ever wanted to use the SQL Trace system stored procedures instead of Profiler, but got intimidated by the cryptic system stored procedure calls? Then this article is just for you. It will show you how to use SQL Trace system stored procedures and provide you with wrapper stored procedures, that can be used to quickly get server side traces up and running.
Steve Jones takes a first look at the next version of SQL Server. It's been sitting for some time, but with the NDA lifted, here's some first impressions of the tools.
Andy started writing about worst practices a long time ago and returns this week with one that is short and sweet - why defining rows that exceed 8060 characters is a very bad idea and how you can avoid it.
This service pack contains bug fixed, plus enhancements including test email button, sorting, and drill down.
Needing to number rows with a sequential id is a pretty common request. Sometimes it's because the user hasn't made the transition to 'set based' thinking, sometimes it really is a valid request (more or less!). Greg provides several different techniques to help you achieve sequential numbering.
This article proposes a system where extra data is stored in a simple row based table and retrieved using the 'store key'. It's not a new concept of course, but the author explains how and why he chose to implement. Feedback should be interesting!
Kumar discusses the differences between scale up and scale out, then does a very good walk through of how to build a scale out solution.
This is one of the vendors we met at PASS 2003. Their new driver is supposed to be faster than the driver provided by Microsoft AND supports NT authentication. Link takes you to a comparision chart of features. (Not Reviewed)
Most of us know what it is, or do we? Chris works on a good definition and along with that, gets into a good look at the problems denormalization creates and talks about a pretty common form of it - the indexed view.
Andy wrote up some notes about the recent PASS Community Summit, plans for next year, people we met, and much more.
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
A bali trip is a dream vacation for travelers who want to experience beautiful...
A bali trip is a dream vacation for travelers who want to experience beautiful...
Comments posted to this topic are about the item Where Your Value Separates You...
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