Viewing 15 posts - 44,896 through 44,910 (of 59,101 total)
There is no need for the RBAR of a function to generate random integer values. The only reason you think so is because you found out that RAND returns...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2009 at 6:57 pm
See the following articles... the first one explains some of the performance problems with using PIVOT instead of building good ol' fashioned cross-tabs and the second one explains one method...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2009 at 6:32 pm
I'm with Gail... WHY do you want to do this to a perfectly good database? What are the business reasons for this?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2009 at 6:28 pm
Your IF statements are fine and they don't require the use of dynamic SQL.
My big question would be... why do you have separate tables for all that stuff?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2009 at 6:18 pm
Why would you need to loop to do effective mortgage rates?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2009 at 5:29 pm
Perry Whittle (3/1/2009)
hey Jeff fancy seeing you in this thread 😉 LOL
Heh... I've not been as active on this forum in the last 2 weeks as I normally am... ya...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2009 at 11:12 am
Thanks, Lowell... that's an awesome compliment. They'd probably just make the same excuses as everyone else, though... things like "it's good enough for what we want to do" or...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2009 at 11:09 am
alexander.yuryshev (3/1/2009)
Jeff Moden (3/1/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2009 at 11:06 am
Heh... and IMHO, CLR's have virtually no place including UDF's. RegEx and file handling are the only two places I've not been able to beat a CLR with T-SQL.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2009 at 9:49 am
Ross McMicken (3/1/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2009 at 9:32 am
Stanley Pagenel (2/28/2009)
Thanks Jeff my problem is fixed now
Yeah, I saw how you think you fixed it on the other thread of yours... lemme tell you the same thing I...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2009 at 9:26 am
Stanley Pagenel (2/28/2009)
Thanks Dugi that help me fix my problem.Have a nice day,
Stan
Nope... if all you've done is replace a Cursor with a Temp table and While loop, all you've...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2009 at 9:25 am
GilaMonster (2/28/2009)
Jeff Moden (2/27/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 28, 2009 at 8:33 am
Here's one, straight from the horse's mouth....
http://technet.microsoft.com/en-us/library/ms131075.aspx
The part that they left out is that there's normally a way to do the same thing in more than 95% of the case...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 9:46 pm
Google "UPSERT SQL SERVER 2005".
Basically, you need both an UPDATE and an INSERT. Both would have joins between the two tables. For the UPDATE, if the join succeeds,...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2009 at 9:36 pm
Viewing 15 posts - 44,896 through 44,910 (of 59,101 total)