Brief Intro to Indexes and INCLUDE – TSQL Tuesday #10!
Content rating: Beginner
This blog was originally posted on December 17, 2009. I’ve pulled it out of the closet for...
2010-09-14
669 reads
Content rating: Beginner
This blog was originally posted on December 17, 2009. I’ve pulled it out of the closet for...
2010-09-14
669 reads
SQL Saturday: All the COOL kids are doing it!
It’s only twelve days until SQL Saturday #52 in Colorado! I’ll be...
2010-09-13
706 reads
Let’s say that you have a staging table, that then loads to a destination table in the same database. If...
2010-09-13
535 reads
As we’ve seen in recent DBARant-able tales, not everyone is completely familiar with methods of restoring SQL backup files to...
2010-09-08
1,713 reads
Today let’s expand on the logical processing order of SELECT that I mentioned in last week’s N Things Worth Knowing...
2010-08-31
2,554 reads
If you haven’t messed with them yet, you should know that CTEs (Common Table Expressions) - new in SQL Server 2005...
2010-08-26
1,287 reads
SELECT is this kind of Swiss Army Knife
SELECT is our bedrock, our foundation, our now-and-forever T-SQL multitasker…and it’s one of the...
2010-08-23
1,210 reads
Piggybacking tangentially off of Tim Mitchell’s (blog, Twitter) SSC editorial Turn a Bad Job into a Good Experience…yesterday I got...
2010-08-17
662 reads
One of the things about SSRS that irritates me is that in the graphical editor, you have to set the...
2010-08-13
1,846 reads
This has come up several times in the course of the last TWO jobs, so I’ll put it here for...
2010-08-12
755 reads
By Arun Sirpal
Do you know what happens when you enable zonal redundancy for your SQL managed...
By Kevin3NF
Why You Shouldn’t Overlook This Quiet but Critical SQL Server Setting If you’ve...
By Steve Jones
The PASS Summit goes on tour this year, with the final date the first...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Make your corporate events more engaging with a fun twist. Our booths capture energetic...
I've written this code, but it is showing right now as 2 rows per...
I have this table in SQL Server 2022:
CREATE TABLE CustomerLarge (CustomerID INT NOT NULL IDENTITY(1, 1) CONSTRAINT CustomerLargePK PRIMARY KEY CLUSTERED , CustomerName VARCHAR(20) , CustomerContactFirstName VARCHAR(40) , CustomerContactLastName VARCHAR(40) , Address VARCHAR(20) , Address2 VARCHAR(20) , City VARCHAR(20) , CountryCode CHAR(3) , Postal VARCHAR(20) ) GOIf I check the columns_updated() function return in a trigger, what is the data returned? See possible answers