Editorials

SQLServerCentral Editorial

Double-Entry Bookkeeping for SQL Programmers

All defensive programmers should, in general, avoid unsupported techniques. However, there is a balance to be struck between adherence to 'best practice' approaches to SQL programming, and the need to get the job done. Perhaps certain critical code would benefit from use of the age-old practice of double entry bookkeeping?

3.67 (3)

You rated this post out of 5. Change rating

2010-03-22

974 reads

Blogs

T-SQL Tuesday #191: Invitation–Your Favorite String Parsing

By

It’s that time of the month, and I’m late. My apologies. I had a...

Fabric as a Data Mesh Enabler: Rethinking Enterprise Data Distribution

By

For decades, enterprises have approached data management with the same mindset as someone stuffing...

Truncate Table Pitfalls

By

 Truncate Table Pitfalls Truncating a table can be gloriously fast—and spectacularly dangerous when used carelessly....

Read the latest Blogs

Forums

Technological Dinosaurs or Social Dinosaurs?

By Grant Fritchey

Comments posted to this topic are about the item Technological Dinosaurs or Social Dinosaurs?

DBCC CHECKIDENT

By Steve Jones - SSC Editor

Comments posted to this topic are about the item DBCC CHECKIDENT

Distributed Availability Group Health: T-SQL and Zabbix

By Pablo Echeverria

Comments posted to this topic are about the item Distributed Availability Group Health: T-SQL...

Visit the forum

Question of the Day

DBCC CHECKIDENT

What is returned as a result set when I run this command without a new seed value?

See possible answers