Database Administration

SQLServerCentral Article

Table Partitioning in SQL Server: A Practical Guide to Managing Very Large Tables (VLDBs)

  • Article

Introduction When we first start working with SQL Server, most tables are small enough and we do not think much about their size. But over time, a table can collect millions or even billions of rows. For example, an online shopping application may store every order ever placed, a banking system may retain years of […]

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(1)

You rated this post out of 5. Change rating

2026-11-09

3,165 reads

Blogs

SSMS Is Getting Smarter—and This Isn’t Just About Writing SQL

By

Continuing with my takeaways from SQLCon and FabCon Europe in Barcelona, let’s talk about...

Yippee-Kai-Yay 2027 Summit in Denver

By

Next year the PASS Data Community Summit is in DENVER! and London, but Denver...

PASS Data Community Summit 2026

By

Yesterday was the first day of sessions at the PASS Data Community Summit (after...

Read the latest Blogs

Forums

Pay for Performance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Pay for Performance, which is...

Switching Schemas I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Switching Schemas I

Enforcing Unique Customer Emails When Duplicates Already Exist

By Imran2629

Comments posted to this topic are about the item Enforcing Unique Customer Emails When...

Visit the forum

Question of the Day

Switching Schemas I

I run this query:

SELECT 
 s.name AS schemaname
 , o.name AS objectname
 FROM sys.objects o
 INNER JOIN sys.schemas s ON s.schema_id = o.schema_id
 WHERE o.name = 'Beer'
I get one row back for an object named dbo.beer. There is an ETL schema and both of these are nonpartitioned tables. I run this code:
ALTER TABLE dbo.beer switch TO etl.beer
What happens?

See possible answers