Viewing 15 posts - 16 through 30 (of 42 total)
I did not see the use of CTE included in the comparisons.
June 3, 2015 at 3:26 pm
Missing closing bracket in first subquery?
June 3, 2015 at 3:04 pm
I agree with bringing data in as pure text (varchar) to what I call a "raw data" staging table, before doing the data conversion in another step. One thing...
April 20, 2015 at 10:47 am
NO LOCK will allow reads of "dirty data" -- that's what's meant by "inconsistent data". Read up on why not to use NO LOCK or when it is OK....
April 16, 2015 at 8:59 am
It may be possible if you are using set-based SQL and avoiding cursor loops to use SQL Server's ROW_NUMBER ( ) OVER (ORDER BY ... ) function and add a...
April 16, 2015 at 8:54 am
I would prefer to see most of the same tests in Dev databases as in production, because that would help educate developers (most of whom are not trained to be...
March 23, 2015 at 7:17 am
Also, in addition to the excellent 7 point checklist and other suggestions above, I would check such things as:
TempDB being on a separate set of fast disk...
February 12, 2015 at 5:31 pm
It would be good to see what queries you are comparing and what the physical infrastructure of the two servers.
Also, it would be good to know whether things like TempDB...
February 8, 2015 at 7:22 pm
I disagree that is the difference between recursion and loops or iteration.
"step n+1 does not access all the previously generated rows, but only the
rows generated at step n.
in real...
February 4, 2015 at 10:16 am
In the case of the Fibonacci series calculation (or factorials -- can be done same way), you are right about them winding up being a loop "behind the scenes". ...
February 4, 2015 at 5:04 am
Useful script, but would you ever see a trigger with a CURSOR in it?
No one in their right mind would ever do such a thing, right?
Of course we have seen...
February 3, 2015 at 7:06 pm
Of course you could use ISNULL to convert NULL to '' (empty string).
February 3, 2015 at 4:09 pm
I just used google. Anyone can do that.
February 3, 2015 at 12:59 pm
Things have evolved light years since SQL Server 2000.
CTE's recursion is an ELEGANT, SIMPLE, FAST solution, NOT a sledgehammer.
With SQL Server 2008 or later (and CTE existed in 2005, but...
February 3, 2015 at 12:45 pm
Ah, yes, but things have evolved light years since SQL Server 2000.
CTE's recursion is NOT a sledgehammer.
With SQL Server 2008 or later (and CTE existed in 2005, but not sure...
February 3, 2015 at 12:41 pm
Viewing 15 posts - 16 through 30 (of 42 total)