Technical Article

Using T-SQL CROSS APPLY and OUTER APPLY

That said, even though my personal focus is pretty much OO, I still miss stuff. SQL Server 2005 came out with the CROSS APPLY and OUTER APPLY operators and I have just started learning how to use APPLY in the last month or so. When I think I have it figured out, I am fortunate enough that some of you are interested in reading about my understanding of the technology.

External Article

SQL Server Unique Constraints for Large Text Columns

We are storing large text and URLs that are over 900 bytes in some of our tables and have a requirement to enforce uniqueness in those columns. But SQL Server has a limitation that index size can't be over 900 bytes. How do I enforce uniqueness in these columns and is it possible to achieve this in SQL Server 2005 and above? What are my different options to solve this problem? I heard that we can use CHECKSUM to create a hash, but is it possible to avoid collisions in the hash value as we are storing millions of rows?

Blogs

Monday Monitor Tips: Intelligent Alert Thresholds

By

At the recent Redgate Summit in Chicago, I demo’d (lightly) the ML based Alert...

A New Word: los vidados

By

los vidados – n. the half-remembered acquaintances you knew years ago, who you might...

In-Person CISA Training – April 13-16, 2026

By

I will be leading an in-person Certified Information Systems Auditor (CISA) exam prep class...

Read the latest Blogs

Forums

String_agg not working as needed

By DaveBriCam

I'm trying to get this string_agg to put all the 'comments' into one result...

Vectors in SQL Server 2025

By Daniel Calbimonte

Comments posted to this topic are about the item Vectors in SQL Server 2025

Odd Sequences

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Odd Sequences

Visit the forum

Question of the Day

Odd Sequences

What values are returned from this code?

CREATE SEQUENCE NumericSequence
    AS NUMERIC(5,1)
    START WITH 1.0
    INCREMENT BY 0.1;
GO
SELECT NEXT VALUE FOR NumericSequence
GO
SELECT NEXT VALUE FOR NumericSequence
GO

See possible answers