Editorial

SQLServerCentral Editorial

Clustered Indexes? Sedimentary, my dear Watson

  • Editorial

There is much sound advice suggesting that every table should have a clustered index, and that narrow, integer, ever-increasing columns, such as afforded by an IDENTITY column are the best choice. But is the sedimentary approach really the natural order of the day?

(3)

You rated this post out of 5. Change rating

2010-05-24

457 reads

Blogs

Monday Monitor Tips: AI Query Analysis

By

AI is everywhere. It’s in the news, it’s being added to every product, management...

AI: Blog a Day – Day 8: RAG – Retrieval Augmented Generation

By

RAG — Retrieval Augmented Generation. we have covered so far — embeddings, vectors, vector...

AI: Blog a Day – Day 7: Vector and Vector Databases

By

Continuing from Day 6 we learned Embeddings, Semantic Search and Checks, on Day 7...

Read the latest Blogs

Forums

I'm thinking about submitting some articles

By Doctor Who 2

I've written some documentation on using different Markdown types of files on GitHub. It's...

Not Just an Upgrade

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Not Just an Upgrade

Restoring On Top I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Restoring On Top I

Visit the forum

Question of the Day

Restoring On Top I

I am doing development work on a database and want to keep a backup so I can reset my database. I make some changes and want to restore over top of my changes. When I run this code, what happens?

USE Master
BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO

USE DNRTest
GO
CREATE TABLE MyTest(myid INT)
GO
USE master
RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACE

See possible answers