Database Nonsense - Unstructured Data
Sloppy terminology leads to big misunderstandings. Terms don't get much sloppier than "Unstructured data".
2016-10-25
481 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,658 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,878 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,769 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)
51,235 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,789 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,545 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,644 reads
Blogs
Redgate Summit Comes to the Windy City
By Steve Jones
I love Chicago. I went to visit three times in 2023: a Redgate event,...
Non-Functional Requirements
By Brian Kelley
I have found that non-functional requirements (NFRs) can be hard to define for a...
Techorama 2024 – Slides
You can find the slidedeck for my Techorama session “Microsoft Fabric for Dummies” on...
Forums
AG listener cant be removed
Testing with AG on Linux with Cluster=NONE. it was all going ok and as...
Remove comma inside Comma Delimited File csv in SSIS Using Script task
Hi, I have two tables: one for headers with 9 fields and another for...
Inserting 100K rows Performance - Baseline Performance
We're trying to understand how quick new versions of SQL server can be. Obviously...
Question of the Day
The "ORDER BY" clause behavior
Let’s consider the following script that can be executed without any error on both SQL Sever and PostgreSQL. We define the table t1 in which we insert three records:
create table t1 (id int primary key, city varchar(50)); insert into t1 values (1, 'Rome'), (2, 'New York'), (3, NULL);If we execute the following query, how will the records be sorted in both environments?
select city from t1 order by city;See possible answers