Managing Large Data Sets in SQL Server 2005 and 2008
Easily manage operations against large data sets, be able to stop and start operations at a whim and throttle them up or down to manage system performance.
Easily manage operations against large data sets, be able to stop and start operations at a whim and throttle them up or down to manage system performance.
In which Phil Factor attempts to justify his iPhones and iPod Touches as a business expense.
Over the last few weeks I have focused most of my blog energy into writing a couple articles. So I...
Today we have a guest editorial from Grant Fritchey. The Boy Scouts motto is "be prepared" and most of you probably unconsciously follow that in your daily lives. Why is it that so many of us don't follow through on this same advice with our databases? Grant Fritchey gives a few examples of how you should "be prepared" for a database emergency.
Today we have a guest editorial from Grant Fritchey. The Boy Scouts motto is "be prepared" and most of you probably unconsciously follow that in your daily lives. Why is it that so many of us don't follow through on this same advice with our databases? Grant Fritchey gives a few examples of how you should "be prepared" for a database emergency.
Today we have a guest editorial from Grant Fritchey. The Boy Scouts motto is "be prepared" and most of you probably unconsciously follow that in your daily lives. Why is it that so many of us don't follow through on this same advice with our databases? Grant Fritchey gives a few examples of how you should "be prepared" for a database emergency.
In this article, we are going to focus on writing or refactoring the data access codes using the best practices. But, before we start playing the game, we need to prepare the ground first. So let’s do the groundwork at this very next step:
Perhaps you heard of or actually tried Windows ReadyBoost in Windows Vista, and were (like me) disappointed with the results?...
The first day of 2010 has Steve Jones blooper reel in addition to some well wishes.
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...
Comments posted to this topic are about the item Where Your Value Separates You...
Comments posted to this topic are about the item Fixing the Error
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
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