External Article

The Basics of Good T-SQL Coding Style

TSQL Code must work properly and efficiently. That's not enough though. Unless you are working alone, have perfect memory and plan to never change job, then you need to comment and document your code, it must be inherently readable, well laid out, use informative and obvious names, and it must be robust and resilient; written defensively. It must not rely on deprecated features of SQL Server, or assume particular database settings. Robert Sheldon starts a series of articles that explains the basics.

Blogs

Upgrading SQL Server Containers on the Laptop

By

I don’t have SQL Server installed on my laptop. In an effort to keep...

How to Find Expensive Queries in Amazon Redshift

By

Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...

The Notification Trap: How Input Fatigue Is Killing Deep Work in Tech

By

If you've been here before, you know this blog is usually about SQL Server,...

Read the latest Blogs

Forums

Layanan wa Qlola bri

By advanceesthe

Layanan support QLola BRI tersedia melalui WhatsApp 08136035412 untuk membantu berbagai kebutuhan Anda, mulai...

Pusat bantuan qlola bri resmi

By advanceesthe

Layanan bantuan QLola BRI melalui whatsapp 628136035412 Layanan bantuan QLola BRI kini lebih mudah...

Call center Qlola bri

By advanceesthe

Butuh bantuan QLola BRI? Hubungi WhatsApp 08136035412 untuk layanan cepat seputar login, transaksi, dan...

Visit the forum

Question of the Day

How Long is a Long I/O?

In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?

See possible answers