Some reasons for the slow-running of database applications aren't obvious. Occasionally, even the profiler won't tell you enough to remedy a problem, especially when a SQL Statement is being forced to wait. Now, in SQL Server 2008, come XEvents, which allow you to look at those waits that are slowing your SQL Statements. Mario Broodbakker continues his series about SQL Server Wait Events
2008-08-20
2,056 reads
2008-08-06
204 reads
2008-08-04
4,455 reads
This article provides an overview of the use of Column Sets with Spare Columns in SQL Server 2008
2008-07-30
2,422 reads
2008-07-25
2,890 reads
SQL Server 2008 introduces the Database Backup Compression feature. This article describes how to take advantage of this new feature
2008-07-25
2,029 reads
2008-07-17
2,624 reads
2008-07-14
3,412 reads
2008-07-10
2,720 reads
2008-07-10
2,130 reads
Continuing with my takeaways from SQLCon and FabCon Europe in Barcelona, let’s talk about...
By Steve Jones
Next year the PASS Data Community Summit is in DENVER! and London, but Denver...
By Steve Jones
Yesterday was the first day of sessions at the PASS Data Community Summit (after...
Comments posted to this topic are about the item Pay for Performance, which is...
Comments posted to this topic are about the item Switching Schemas I
Comments posted to this topic are about the item Enforcing Unique Customer Emails When...
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.beerWhat happens? See possible answers