Viewing 15 posts - 38,716 through 38,730 (of 59,098 total)
David Portas (4/27/2010)
TheSQLGuru (4/27/2010)
Tables are UNORDERED sets of data unless they have a CLUSTERED INDEX on them.
Tables are unordered sets even if they do have a clustered index. A clustered...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2010 at 9:30 am
TheSQLGuru (4/27/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2010 at 9:27 am
jose-276033 (4/27/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2010 at 6:59 am
aaa-322853 (4/27/2010)
If you use a tally table you can...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2010 at 6:44 am
aaa-322853 (4/26/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2010 at 3:51 pm
striker-baba (4/23/2010)
My Sr.dba says we can truncate the log no backup is required..
.
.
what do you suggest.?
I'd suggest that you stop trying to do a DBA's job. Seriously... the DBA...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2010 at 2:04 pm
aaa-322853 (4/26/2010)
Ah... no. CTE's are absolutely wonderful for building "top down", highly readable, highly effective code. I just wouldn't build a...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2010 at 1:51 pm
eseosaoregie (4/26/2010)
Managed to run the amendments this afternoon and found considerable improvement in performance. Whole thing loaded in just under 2min 30sec. Network traffic is high during that period...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2010 at 12:28 pm
Paul Morris-1011726 (4/26/2010)
EX 1 = A, 2 = B,...27 = AA, 28= BB,... 53 = AAA, 54 = BBB,...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2010 at 11:49 am
Another stunning example of how an article should be written as well as how to back up all claims with code. Very well done, Paul.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2010 at 11:44 am
You bet. Thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2010 at 10:57 am
aaa-322853 (4/26/2010)
So lets start with Table Variables. Basicially never use these, regardless of the row size or application (unless it's a UDF)....
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2010 at 10:43 am
Holy moly... Guess I needed to read the entire graphic and the underlying text, huh?
Again, IMHO, using Global Temporary Tables is a form of "Death by SQL" because if two...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2010 at 7:18 am
Gahh.... I'd also recommend that if you need to reference data more than once from a subquery that you NOT use CTE's... Like Views, if you reference a CTE more...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2010 at 7:14 am
It's simply not a given that Table Variables are faster than Temp Tables and Table Variables are a whole lot more difficult to troubleshoot because their content don't persist even...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2010 at 7:11 am
Viewing 15 posts - 38,716 through 38,730 (of 59,098 total)