Viewing 15 posts - 39,751 through 39,765 (of 59,072 total)
john-902052 (2/15/2010)
Not sure what you are talking about. I am using 2005 not 2008 SQL Server.
Hmmm... sorry about that, John. How did you get the INSERT/VALUES statement to...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 16, 2010 at 6:03 am
I wouldn't check just one zip code at a time and I wouldn't split the 24 million row table up. Correctly written queries and joins in the presence of...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2010 at 8:34 pm
You should pre-aggregate (thank you Peso) the data by month and status and dump it into a temp table. Then, even the worst performing running total method will work...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2010 at 7:30 pm
Chris,
Both answers above are technically correct but if you want a coded answer, you'll need to change this...
Mea Webb t0022165 1 2010-02-15 00:00:00.000 0
Carlos Banuelos t0021988 1 2010-02-15 00:00:00.000 0
Vijay...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 15, 2010 at 7:17 pm
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
Viewing 15 posts - 39,751 through 39,765 (of 59,072 total)