Viewing 15 posts - 27,001 through 27,015 (of 59,101 total)
Dreamsz (4/15/2013)
Thanks for looking into my post, well I been scratching my head for a long time now the requirement which sound pretty simple turned out to be a...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2013 at 4:44 pm
True, but the link is still helpful to others that might find this thread.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2013 at 4:21 pm
Glad to help. Thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2013 at 4:18 pm
Pravasis (4/15/2013)
I was exactly looking for something like
The bottom line here is to make sure the data in the join columns is "right sized" for maximum efficiency.
.
Thanks...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2013 at 4:15 pm
The Wizard Of Oz (4/15/2013)
I've seen plenty of DISTINCT code that had some dodgy JOINs, or bad assumptions about the underlying data relationships.
I was only hazarding...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2013 at 4:08 pm
The Learner (4/15/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2013 at 4:06 pm
Eric M Russell (4/15/2013)
ulisseslourenco (4/12/2013)
I have a question about nolock. I work in a company that there is a rule: all select query we must put nolock. If we...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2013 at 4:00 pm
Thank both of you for your thoughtful feedback and for the experiments you've done with the data.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2013 at 3:56 pm
I kinda figured it was something like that. Thanks for the feedback, Benson. And thanks for the reads on my articles. I aim to please. I...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2013 at 3:54 pm
KoldCoffee (4/2/2013)
Thank you David...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2013 at 10:01 pm
Sergiy (4/8/2013)
Jeff Moden (3/27/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2013 at 9:49 pm
The Learner (12/13/2012)
Of course - makes total sense! Thanks for the tip.
I know it's an old post but you don't usually need to drop Temp Tables in a stored procedure....
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2013 at 5:16 pm
Thanks for sharing your code but it just doesn't need to be so complex a thing. SQL Server will handle all sorts of date formats without any help. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2013 at 4:49 pm
Thank you for your effort but your code doesn't actually work as claimed. Try the following and see why. You need to go back to Books Online and...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2013 at 4:32 pm
Please consider using a Tally Table instead of a recursive CTE to count. Please see the following article as to why.
http://www.sqlservercentral.com/articles/T-SQL/74118/
If you don't know what a Tally Table (or...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 14, 2013 at 4:02 pm
Viewing 15 posts - 27,001 through 27,015 (of 59,101 total)