Database Nonsense - Unstructured Data
Sloppy terminology leads to big misunderstandings. Terms don't get much sloppier than "Unstructured data".
2016-10-25
577 reads
Don Peterson
Is XML the Answer?
New Author! Don Peterson writes his first article for us and explores why he considers XML to be...bad! There are some interesting points made here and if you've haven't thought about what XML means to you as a DBA, it's a subject worth spending some time on.
2008-05-02 (first published: 2003-10-07)
64,749 reads
Thoughts on the PASS Summit
The 2007 PASS Summit is coming up in September and you can register early and save now, but is it worth going? Longtime author and successful DBA Don Peterson brings us a few thoughts on last year's Summit and the benefits of attending.
2007-02-19
1,894 reads
Beware of Search Argument (SARG) Data Types
Performance tuning often seems like it can be more of an art than a science. However there are a number of fundamentals that can help you tune most of the queries that you will write or have issues with their performance. Don Peterson brings us a look at how he tuned a query in the real world to avoid a conversion that can cause a query to run slower.
2006-07-13
11,855 reads
Lookup Table Madness
Are you mad? Not angry, more like crazy when it comes to designing databases in SQL Server? Don Peterson has met a few people he thinks are just that when it comes to building lookup tables. Does it stem from poor understanding of database design? Or do you disagree? Read Don's case against this particular design practice.
2006-03-24 (first published: 2004-09-08)
52,258 reads
All About Transactions - Part 3
Transactions in SQL Server are probably no more complicated than those in other RDBMS products, which is to say they are fairly complex. Don Peterson continues with part 3 of his series and takes a look at transaction isolation levels and how they interact with multiple connections and their impact on locking.
2004-12-02
15,935 reads
All About Transactions - Part 2
Transactions in SQL Server can be very complicated, and are often misunderstood. Don Peterson brings us part 2 of his series on transactions. This part deals with XACT_ABORT, compilation errors and error handling in transactions.
2004-11-24
19,707 reads
All About Transactions - Part 1
The heart of an RDBMS is the transaction system that it employs. SQL Server has a great one that can easily be misunderstood or misused by those that haven't spent time delving into the details of how it works. Don Peterson has done that and brings us the start of a new series on the details of how transactions work in SQL Server.
2004-11-15
24,889 reads
Blogs
Tech Conferences and Expanding Your View
By Brian Kelley
Tech conferences aren't just for networking and learning how to address a problem you're...
Managing subscribers, creating newsletters
By DataOnWheels
When I created the website on WordPress, I was expecting all the features I...
Finding the Last Last Name in SQL: #SQLNewBlogger
By Steve Jones
I wrote a piece on the new SUBSTRING in SQL Server 2025 and got...
Forums
Email change does not work
I changed my email address in Edit Profile page, but it has no effect...
The case for "Understanding our business" training
Comments posted to this topic are about the item The case for "Understanding our...
Specifying the Collation
Comments posted to this topic are about the item Specifying the Collation
Question of the Day
Specifying the Collation
I am dealing with issues on my SQL Server 2022 instance related to collation. I have an instance collation of Latin1_General_CS_AS_KS_WS, but a database collation of Latin1_General_CI_AS. I want to force a few queries to run with a specified collation by using code like this:
DECLARE @c VARCHAR(20) = 'Latin1_General_CI_AS'
SELECT p.PersonType,
p.Title,
p.LastName,
c.CustomerID,
c.AccountNumber
FROM Person.Person AS p
INNER JOIN Sales.Customer AS c
ON c.PersonID = p.BusinessEntityID
COLLATE @c
Will this solve my problem? See possible answers