Viewing 15 posts - 33,871 through 33,885 (of 59,099 total)
Jeff Moden (5/22/2011)
Henk Schreij (5/22/2011)
Jeff, you're right, thank you for your explanation.Sorry for my bold comment. :unsure:
I knew I should have added a smiley face or something. 😀 ...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2011 at 4:28 pm
Henk Schreij (5/22/2011)
Jeff, you're right, thank you for your explanation.Sorry for my bold comment. :unsure:
I knew I should have added a smiley face or something. 😀 I took...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2011 at 4:24 pm
GilaMonster (5/22/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2011 at 3:41 pm
Shai Bar-Lev (5/22/2011)
Thanks for the sample SQL code.
I'll be by the customer site and will test both approaches. sample data is a problem due to the nature of...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2011 at 12:21 pm
tuseau (5/22/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2011 at 12:09 pm
Thomas Abraham (5/18/2011)
In general, I'm becoming a fan of your posts.
Thanks for the great feedback, Thomas. :blush:
If I had a son, I'd name him Million Row Table in your...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2011 at 11:55 am
The reason why I use a Temp Table for such things is because a Temp Table persists in SSMS until I drop the table or end the session. There...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2011 at 11:36 am
Very well done Rob and Steve! Rob, I hope you do get a precon!
I wish more people would understand what "tuning" is all about. It's not about getting SQL...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2011 at 11:24 am
Wayne is absolutely spot on about the possible performance problem associated with joined UPDATEs. The "target" of the UPDATE MUST be somewhere in the FROM clause (I usually make...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2011 at 10:07 am
abhi620 (5/20/2011)
i think this is good solution for...
With only very few exceptions, the RBAR of a WHILE loop is almost never a good solution. Please try it on a...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2011 at 10:06 pm
Ninja's_RGR'us (5/18/2011)
Select into could cause recompiles and slow you down.
True enough and I do realize you said "could" but just to be sure... The blinding speed of a SELECT/INTO...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2011 at 11:08 am
Henk Schreij (5/21/2011)
Till that moment my mind was struggled...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2011 at 10:43 am
a-elnajjar (5/21/2011)
I am Front End Web Developer. I never use SQL Server since I graduate from school and I really need some Help From Database Gurus .I am...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2011 at 10:40 am
Jeff Moden (5/20/2011)
WayneS (5/20/2011)
Very nice Sean.
One thing to point out (for all solutions for this) is that if you have a case-sensitive collation, you will want to force the strings...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2011 at 4:09 pm
WayneS (5/20/2011)
Very nice Sean.
One thing to point out (for all solutions for this) is that if you have a case-sensitive collation, you will want to force the strings to be...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2011 at 4:08 pm
Viewing 15 posts - 33,871 through 33,885 (of 59,099 total)