Viewing 15 posts - 32,026 through 32,040 (of 59,102 total)
kramaswamy (11/7/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2011 at 7:58 am
I didn't look back to see but do you have the xp_CmdShell proxy set up?
Also, is this a direct connection or are you "talking" through more than one connection?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 7, 2011 at 7:35 am
SQL Kiwi (11/6/2011)
I don't agree that recursive CTEs are RBAR by the way: they're simply set-iterative, a bit like Hugo's 'lasagne' running total code.
I have to agree to disagree then......
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2011 at 9:40 pm
SQL Kiwi (11/6/2011)
Recursive CTEs can be made to perform extremely well;...{snip}...And there's also a 'super-fast' DISTINCT (by me!) that Jeff may recall:
That is a remarkable bit of code, indeed. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2011 at 9:18 pm
SQLRNNR (11/6/2011)
Jeff Moden (11/5/2011)
SQLRNNR (11/3/2011)
I have seen them perform marvelously as well....
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2011 at 7:59 pm
MonkeyMan (11/5/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2011 at 7:22 pm
Thanks for taking the time to provide the feedback. Based on what you said, unless rounding is somehow important to that other stored procedure, I wouldn't bother formatting the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2011 at 4:38 pm
JonFox (11/6/2011)
That's great stuff Jeff! I love this forum, I keep learning better ways to do things. 🙂
Thanks Jon, but I have to really stop typing at 2 in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2011 at 4:31 pm
SQL Kiwi (11/6/2011)
Jeff Moden (11/6/2011)
My main purpose in this is to show that what SQL Server labels as a SCAN is frequently a SEEK in disguise.
The query plan I get...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2011 at 4:26 pm
You folks know me... I'll be one of the first to use a "Pseudo-Calendar" table if it's warrented. I don't believe it is in this case. We also...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 6, 2011 at 12:38 am
richard garth (11/5/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2011 at 3:55 pm
Beginner_2008 (11/5/2011)
id,
firstname,
lastname,
transactionamount
table2 has
id,
fullname,
transactionamount
How to compare the firstname,lastname with fullname
And after comaprision check whether the full name is 70% of the the both firrstname and lastname.
Example:
firstname: William
lastname: John
Fullname:...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2011 at 3:46 pm
amigoface (11/5/2011)
the context : i have to migrate a database appliation from firebird to SQL server
the original database contain a stored procedure that use a formating function that doesn't...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2011 at 3:40 pm
For us, it was important that any change made by any method had to be detected and that the appropriate rows where enddated as part of the transaction that did...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2011 at 9:29 am
SQLRNNR (11/3/2011)
I have seen them perform marvelously as well. For instance...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2011 at 8:38 am
Viewing 15 posts - 32,026 through 32,040 (of 59,102 total)