Tag Info

New answers tagged

0

cluster command is a table rewrite process. So, yes it will cluster anything on the table, including extended storage.


1

You can specify the name for a clustered primary key if you add it as a separate constraint: CREATE TABLE dbo.YourTable ( idBenchmark int NOT NULL IDENTITY (1,1), .... other columns .... CONSTRAINT PK_YourTable PRIMARY KEY CLUSTERED(idBenchmark) ) and then you should have no trouble at all to drop it if needed.


4

Go ahead and drop the clustering key while you're importing data. When you've finished your INSERTs, create the clustering key first, then the PK if it's non-clustered, then any remaining indices. I'm running such scripts at this very moment, and it takes about half as long as inserting into a table which is fully indexed. There's no problem in going ...


2

If you have a clustered (or covering) index starting with (Key1, Key2, Key3, ...) on the table that the CTE is querying, this should be a well-performing query. Can you add a "Key4", preferably an identity column, in the source table to your non-unique clustered index, so you perhaps can make the index unique? That way, you could also set "Key4" as your ...



Top 50 recent answers are included