Editorials

SQLServerCentral Editorial

13 Disasters

This editorial that was originally published on Aug 15, 2007. It is being rerun as Steve is traveling. This editorial looks at the issues that happen in production and how you should perhaps plan for disasters.

You rated this post out of 5. Change rating

2012-06-11 (first published: )

255 reads

SQLServerCentral Editorial

Tuning People?

Database people are used to changing the hardware of the server on which a problem database resides, or making changes to indexes and database settings, but humans and their organisations are far more difficult to tune and optimise than databases.

(6)

You rated this post out of 5. Change rating

2012-06-11

298 reads

Blogs

App-Consistent MongoDB Snapshots Across Multiple Pure Storage FlashArrays

By

Introduction When you’re running MongoDB at scale with data distributed across multiple Pure Storage...

PASS: Quantum Computing Slides

By

If you're an attendee at the PASS Data Community Summit this year, there are...

A New Word: Dead Reckoning

By

dead reckoning– v. intr. finding yourself bothered by somebody’s death more than you would...

Read the latest Blogs

Forums

Filtered Indexes: The Developer’s Secret Weapon in SQL Server

By Chandan Shukla

Comments posted to this topic are about the item Filtered Indexes: The Developer’s Secret...

Is Data Modeling Common?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Is Data Modeling Common?

Getting The Database Name

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Getting The Database Name

Visit the forum

Question of the Day

Getting The Database Name

I run this code to connect to SQL Server 2022 from the command line.

sqlcmd -S localhost -E
At the command line, I run these two commands:
SELECT ORIGINAL_DB_NAME()
GO
What is returned?

See possible answers