Viewing 15 posts - 39,781 through 39,795 (of 59,098 total)
Herman,
You're new so just a tip for you... Both of the answers above are technically correct but if you want a coded answer, take a look at the article at...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2010 at 7:13 pm
john-902052 (2/15/2010)
INSERT INTO [ClientManager].[dbo].[Fees]
([FeeDesc],[FeeAmount])
VALUES
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2010 at 7:07 pm
What happens if you reverse the order between the two methods?
I'm thinking that cache helped the second one... a lot.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2010 at 6:21 pm
Percentages? Even on Tera-byte drives?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2010 at 6:02 pm
deveringham (2/15/2010)
Hi LutzThe updated code worked a treat (first time) - thank you
Dougal
The next question would be, do you understand how it works and could you use it to solve...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2010 at 5:57 pm
I'm not sure how you'd use substring in conjunction with something that doesn't return a starting position for the found string.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2010 at 5:53 pm
stan.teitelbaum (2/15/2010)
perhaps because it increases randomness by not allowing dupes between negatives and positives? Perhaps also...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2010 at 2:01 pm
Gotta love it. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2010 at 9:23 am
Mohamed Asane (2/15/2010)
much of thanks Fazalul Haque n all..nice effort..
got a solution..
So... post your solution, please. Two way street here.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2010 at 6:36 am
phumlo1 (2/15/2010)
Got the answer. thanx
Cool... so what's the answer?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2010 at 6:33 am
Heh... the correct answers are actually missing for all versions.... "Based on Model" and "Too Small". 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2010 at 6:59 pm
lmu92 (2/14/2010)
Shouldn't it be on (EmployeeID, SalaryDate) instead of RowID?
What would happen with rows like:
SELECT 1, 12, '20050101',...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2010 at 6:52 pm
Do it all at once and without a triangular join...
CREATE CLUSTERED INDEX IX_SalaryHistory_RowID
ON #SalaryHistory (RowID)
DECLARE @PrevSalaryAmount MONEY
UPDATE #SalaryHistory
SET @PrevSalaryAmount...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2010 at 5:30 pm
As a side bar, I probably wouldn't ever have a period table based on the last whole day of the month... if "times" ever creep into the statement table, then...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2010 at 10:28 am
lmu92 (2/14/2010)
Looks like I'm getting too addicted to CTEs... 😛
No... don't think that for a minute. The CTE's you wrote are a great exhibition of "Divide'n'Conquer". They run...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 14, 2010 at 9:40 am
Viewing 15 posts - 39,781 through 39,795 (of 59,098 total)