Viewing 15 posts - 37,831 through 37,845 (of 59,072 total)
GilaMonster (6/30/2010)
Jeff Moden (6/30/2010)
... but don't mind giving a little advice on what to change. ๐The entire thing? ๐
Heh... z'actly. ๐
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2010 at 6:46 am
Outstanding. Always makes my day when someone can apply something they learned from one of my articles. Thanks for the great feedback.
On the other stuff... I'm one of...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2010 at 6:44 am
sudhakara (6/30/2010)
Jeff Moden (6/30/2010)
PaulB-TheOneAndOnly (6/30/2010)
sudhakara (6/30/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2010 at 6:37 am
If you have the Enterprise Edition, now would be a really good time to make the choice as to how to partition the table.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2010 at 6:17 am
Agreed.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2010 at 6:13 am
We drove secondary ads for Expedia.com. A single SQL Server handled things just fine. It was more important to balance 3 identical web servers that had a pretty...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2010 at 6:10 am
niall.baird (6/30/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 9:25 pm
What is the reasoning behind NOT showing 101?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 5:12 pm
I forget who I got this one from but I've never found anything simpler for correctly calculating age in years. Using Lynn's good test harness...
CREATE TABLE #T(Id INT,date1 DATETIME,date2...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 5:05 pm
PaulB-TheOneAndOnly (6/30/2010)
sudhakara (6/30/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 4:15 pm
david_wendelken (6/30/2010)
It's also easier to comment out a line starting with a comma when debugging.
Actually, it's not. It's only easier to comment out the last line with leading commas....
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 3:41 pm
Heh... almost 1000 lines of trigger code with cursors and multiple table updates with some pretty nasty joins and you wonder why there are deadlocks occurring. My suggestion would...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 3:30 pm
davec-640463 (6/30/2010)
Jeff Moden (6/30/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 7:57 am
Minaz Amin (6/29/2010)
Try using GROUPING SETS ,ROLLUP or CUBE with group by function.
Agreed and Spot On.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 7:37 am
leonardo_gt (6/30/2010)
To obtain a single value as a result of an operation...
That's normally the end of any chance at performance. Stop thinking about what you want to do to...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2010 at 7:33 am
Viewing 15 posts - 37,831 through 37,845 (of 59,072 total)