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

Overcoming Imposter Syndrome: A Plan

By

My most recent bout with imposter syndrome was with ISACA’s Digital Trust Ecosystem Framework...

Advice I Like: Celebrate Success

By

“On the way to a grand goal, celebrate the smallest victories as if each...

Programmatically Retrieving MLV Lineage and Refresh Times

By

Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...

Read the latest Blogs

Forums

BCA KCP Rajawali No.Telp:087757645171

By Xay Nha Nhanh

Whatsapp:087757645171 Jl. Rajawali 53 G, Krembangan Sel., Kec. Krembangan, Surabaya, Jawa Timur 60175

BCA KCP Kas City Resort Hub.0813•7887•595

By JBUAS

BCA KCP Kas City Resort Hub.0813•7887•595.Komp, Jl. City Resort Residence Boulevard Ruko Miami, Jl....

BCA KCP Mangga Besar VIII Telp:cs.(0821)8171955

By telediousnom7887

Whatsapp:08218171955 Jl. Mangga Besar VIII, BB CC No.11, Daerah Khusus Ibukota Jakarta 11150

Visit the forum

Question of the Day

Increase Deadlock Detection

How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?

See possible answers