As has been noted, the tables are definitely wrongly clustered, and that is causing the bad performance. Because, as has also been noted, of the "junior error" of assuming...

Or this:

SELECT

OBJECT_NAME(fkc.parent_object_id) AS [Referencing Table],

fkc.parent_object_id AS [Referencing Object ID],

OBJECT_NAME(fkc.referenced_object_id) AS [Referenced Table Name],

fkc.referenced_object_id...

Maybe as below? I think you've overly complicated the date selection and caused the duplicates.

For best performance, the Diskspace_Global table should probably be clustered either on Date_ (with the...

First, create a "standard" tally table (a table of sequential numbers). I can't provide code because the filter thinks it's "sql injection". After creating the tally table, then...

hlsc1983 (10/19/2015)

---

hi am back after a long time . so sorry for that. Now i need to enter 'Marks ' . Each student will have two types of marks for...

I think I understand. You can get all the collectors from a single query, but you have to include the collector in a GROUP BY:

SELECT Collector, COUNT(DISTINCT LoanID) AS...

Script out that index first so you can easily re-create it later if you need to. The index definition itself could still be OK.

That's actually a "good error", in...

Absolutely. If a NULL means 0, then actually put 0, not NULL. NULL is ambiguous, zero is not. If you compress the row, either value won't take...

I would allow NULLs if it's possible a value won't be known. Sometimes unknown is not the same as zero. For example, I might not know the sales...

You don't need MERGE, use UPDATE instead:

UPDATE tt1

SET DealershipName = TT2.[DealershipName],

DealershipAddress = TT2.[DealershipAddress]

FROM TEST_TABLE1 tt1

INNER JOIN TEST_TABLE2 tt2 ON TT2.DealershipCode = TT1.DealershipCode;

Rather than a dynamic trigger, you need dynamic code that generates a static trigger.

That is, after the table is created, run code that dynamically analyzes that table definition and generates...

For one thing, "save to table" is a lot of overhead. Save it to file(s) instead, then load the file(s) into tables later to analyze.

For absolute max speed, you should also cluster the temp table on ID:

SELECT TOP (0) IDENTITY(int, 1, 1) AS ID, ClustKey1, ClustKey2 --, ...

INTO #TEMP

FROM F_POLICY_TRANSACTION

CREATE CLUSTERED INDEX TEMP__CL ON...

When you create the temp table, i.e before it's loaded, cluster it on ( COUNT, MESS ). A nonclustered index will not be efficient. That will speed up...

So is the clustered index on the table permanent, and you just add nonclustered indexes? The clustered index is the most critical index. The best clustered index keys...