Viewing 15 posts - 4,696 through 4,710 (of 7,597 total)
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...
October 21, 2015 at 5:06 pm
hlsc1983 (10/19/2015)
October 21, 2015 at 8:57 am
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...
October 16, 2015 at 12:06 pm
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...
October 16, 2015 at 10:20 am
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...
October 15, 2015 at 2:47 pm
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...
October 15, 2015 at 1:40 pm
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;
October 14, 2015 at 9:59 am
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...
October 13, 2015 at 10:16 am
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.
October 13, 2015 at 10:14 am
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...
October 13, 2015 at 10:02 am
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...
October 12, 2015 at 3:22 pm
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...
October 12, 2015 at 3:17 pm
I don't have time to line up all the columns, but here's the general format of what you need. I don't see where the computed @FT* values are being...
October 12, 2015 at 3:02 pm
Eric M Russell (10/12/2015)
Kristen-173977 (10/9/2015)
Eric M Russell (10/9/2015)
October 12, 2015 at 11:54 am
Even more important would be properly (uniquely) clustering the tblRecipeAllergen table on ( Recipe_number, Allergen ) (and removing AllergenId from the table, as it's not needed).
October 9, 2015 at 1:24 pm
Viewing 15 posts - 4,696 through 4,710 (of 7,597 total)