Editorial

SQLServerCentral Editorial

Double-Entry Bookkeeping for SQL Programmers

  • Editorial

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)

You rated this post out of 5. Change rating

2010-03-22

985 reads

Blogs

Why your data still can’t answer a simple question 

By

Every organization I talk to has the same problem dressed up in different clothes....

T-SQL Tuesday #197 Invitation – An impactful session or two from a conference

By

I am delighted to host this month’s T-SQL Tuesday invitation. If you are new...

Did You Really Name That Default?

By

Ten years (and a couple jobs) ago, I wrote about naming default constraints to...

Read the latest Blogs

Forums

The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI

By Terry Jago

Comments posted to this topic are about the item The day-to-day pressures of a...

SQL 2017 to SQL 2025. Good to Go ?

By homebrew01

We need to replace our Windows server running SQL 2017. Any reason not to...

Using OPENJSON

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Using OPENJSON

Visit the forum

Question of the Day

Using OPENJSON

I have some data in a table that looks like this:

BeerID BeerName    brewer               beerdescription
1      Becks       Interbrew            Beck's is a German-style pilsner beer 
2      Fat Tire    New Belgium          Toasty malt, gentle sweetness, flash of fresh hop bitterness.
3      Mac n Jacks Mac & Jack's Brewery This beer erupts with a floral, hoppy taste
4      Alaskan Amber Alaskan Brewing     Alaskan Brewing Amber Ale is an "alt" style beer
8      Kirin       Kirin Brewing         Kirin Ichiban is a Lager-type beer
If I run this, what is returned?
select t1.key
    from openjson((select t.* FROM Beer AS t for json path)) t1

See possible answers