I thought it did. Doesn't SQL always create an index to enforce a PK?

Don't make it a primary key, just make it a unique, clustered index.

CREATE UNIQUE CLUSTERED INDEX CX_ACC_Name

ON dbo.ACC_STRUCTURE ( ACC_Name )

--naturally chg WITH options as needed

WITH (...

You could:

1) restore the db, and immediately issue a USE <restored_db> command and set the db to single user mode;

2) delete all the users, schemas, etc., that you don't want...

Erland Sommarskog (8/20/2013)

How many...

INSERT INTO #tempTable

EXEC dbo.someStoredProc

Here's one way:

SELECT

DATEADD(MONTH, DATEDIFF(MONTH, 0, c.month), 0) AS Month,

SUM(c.sales) AS Month_Sales

INTO #Monthly_Totals

FROM dbo.Car c

WHERE

c.month >= '20120401' AND --chg...

What are the results of this query:

SELECT

cpu_count / hyperthread_ratio AS CPUs, *

FROM sys.dm_os_sys_info

Data compression should also be considered, if on Enterprise Edition. [My company has some extremely large audit/logging tables that are rarely read. After compressing them, I often shrink...

Sometimes a database file shrink is indeed needed.

Shrink does not automatically fragment every index. Absolutely you should test for fragmentation after the shrink, and rebuild accordingly, i.e., basically run...

You should also consider putting the quarter as the first key column of the clustered index. Then you won't need to partition in any way as long as you...

Change Tracking or Change Data Capture also might be useful, depending on your specific requirements.

In the context of a LEFT JOIN, yes, the queries would return the same rows from TableA (although, as noted, they might appear multiple times because of the join).

That is,...

You shouldn't have any direct issues from doing that.

First, drop the existing nonclus index, then create the clus index.

Build the index ONLINE if at all possible, to minimize disruption to...

Instead of constantly disabling/enabling the trigger, you can set RECURSIVE_TRIGGERS off for the db, unless you really need recursion for other triggers. In that case, you can use CONTEXT_INFO...

I think DISABLE is far more dangerous, since it applies to every task modifying the table.

Instead you can use CONTEXT_INFO to selectively exit the trigger / skip all/part of the...