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

980 reads

Blogs

TempDB Internals – What’s New (Sql Server 2016 to 2025)

By

I wrote about TempDB Internals and understand that Tempdb plays very important role on...

Blog a Day – Day 2: Generative AI, Multimodal Systems, and Agent AI

By

continuing from Day 1 where we covered the history of AI and GPT family,...

A Wellbeing Day at Redgate

By

It’s a day off for Redgate today. This is our annual wellbeing day, where...

Read the latest Blogs

Forums

A Quick Restore

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Quick Restore

Guarding Against SQL Injection at the Database Layer (SQL Server)

By Terry Jago

Comments posted to this topic are about the item Guarding Against SQL Injection at...

Ola Hallengren Index Optimize Maintenance can we have data compression = page

By JSB_89

I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...

Visit the forum

Question of the Day

A Quick Restore

While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:

USE DNRTest

BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO
/*
Bunch of stuff tested here
*/RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACE
What happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance.

See possible answers