Viewing 15 posts - 47,776 through 47,790 (of 59,102 total)
Heh... well, let's get sneaky, then...
DECLARE @Insert VARCHAR(MAX), @Select VARCHAR(MAX)
SET @Insert = ' INSERT INTO NewTable '
SELECT @Select = COALESCE(@Select + ' UNION ALL','') +...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 13, 2008 at 6:48 pm
Correct... it isn't free. It only consts about $50, though. And, if you get caught using it on a production box, big fines are possible/probable.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 13, 2008 at 4:00 pm
You bet... thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 13, 2008 at 3:38 pm
Garadin (10/13/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 13, 2008 at 9:36 am
Not a good thing to do... the Percentage of Batch is highly unreliable and frequently absolutely incorrect...
Look at the Percentage of Batch on the following code... then run it... SURPRISE!...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 13, 2008 at 9:09 am
Kenney Hill (10/11/2008)
And thanks for pointing out the RBAR aspect of recursive queries. I'm still not very good at spotting hidden RBAR, and you are the master...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 13, 2008 at 8:34 am
Garadin (10/12/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 13, 2008 at 8:26 am
I appreciate your concern about future posts... but more immediately, are you all set with the current post?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2008 at 8:56 pm
Your toast... sorry...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2008 at 8:49 pm
Peso (10/12/2008)
Jeff Moden (10/9/2008)
G Bryant McClellan (10/8/2008)
Michael,Ummm.... both table variables and temp tables start out in memory and "jump" to TempDB when they overcome some point in memory.
Really?
I was under...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2008 at 8:39 pm
Sure... here's one I was "playing" with and never did go back an finish... It stinks because of all the correlated subqueries... probably gonna be terrible for performance.
DECLARE @SomeNumber VARCHAR(25)
CREATE...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2008 at 9:32 am
I would imagine that it would be done the same way as they told me above.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2008 at 9:17 am
GilaMonster (10/12/2008)
And, heh... guess I'm still angry at the fact that the DateTime2, Date, and Time won't convert.
Why? Other than conversions I haven't found a good reason to convert a...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2008 at 9:15 am
PaulB (10/12/2008)
Jeff Moden (10/11/2008)Nope... for a decent size company, that's about what I'd expect except it might be missing the "Project Management" layer.
For some of the small companies I've worked...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2008 at 9:14 am
PaulB (10/12/2008)
Jeff Moden (10/11/2008)
Heh... and by the way... this...T - you do whatever transformation or massaging is needed...
... sometimes means deleting duplicated data. 😉
Nope. We do not delete on Staging....
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2008 at 8:27 am
Viewing 15 posts - 47,776 through 47,790 (of 59,102 total)