SQL Server 2008

Technical Article

Reports for SQL Server 2008 System Data Collections

  • Article

With SQL Server 2008's new Data Collection feature and the Management Data Warehouse (MDW), came three system Data Collection sets. This article covers the different data collection standard reports that have been provided to display information related to the statistics collected by the system data collections.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2008-11-11

2,517 reads

Technical Article

Data Access Tracing

  • Article

Learn how to apply the new tracing functionality in Microsoft data access technologies such as ADO.NET 2.0, MDAC 2.82, SQL Server Native Client, and the JDBC driver; and in the SQL Server network protocols and the Microsoft SQL Server 2005 database engine. You can also download associated sample code for this article.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2008-10-03

2,854 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