Viewing 15 posts - 40,756 through 40,770 (of 59,070 total)
Heh... I agree, Kevin... about cursors and while that's a very good thing, the op learns nothing about the other faults in the code especially the 23:59:59 thing. 😉
Clive, I...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2009 at 6:08 pm
halane34 (12/8/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2009 at 5:45 pm
I have two recommendations on that, Clive... first, post your question as a new post on the T-SQL forum because it'll will like get a better response there instead of...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2009 at 5:37 pm
JRoughgarden (12/8/2009)
All DBMS's are fairly similar; you do the same things with all of them. It's just the syntax that differs some.
When it comes to the differences between RDBMS's like...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2009 at 5:32 pm
Yep... PIVOT will do... here's why I don't use it, though...
http://www.sqlservercentral.com/articles/T-SQL/63681/
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2009 at 5:28 pm
Test-170228 (12/7/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2009 at 7:24 pm
RBarryYoung (12/7/2009)
Scotch & Percocet
Heh... heat it up, add a little lemon and honey, and you have my favorite totie. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2009 at 7:07 pm
I don't have nearly the same intensity problem, but Scotch helps. 😛
Shifting gears... Man, I sure do hope you get better. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2009 at 4:36 pm
Actually, with a bit of fore thought, it's quite easy to build a table that can be referenced as if it were a multidemensional array. It's not a common...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2009 at 9:56 am
GSquared (12/7/2009)
The reason I use cursors for this kind of thing, instead of "quirky update" string building, is that I can wrap each command in error handling much more easily.
You...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2009 at 9:51 am
Which group of customers is having the most influence on the future direction of database systems right now?
Heh... apparently, the wrong ones... look at what they did to Office 2007...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2009 at 6:20 am
SQL Server and all relational databases aren't much more than glorified file handlers. If you accept them as that, then you'll see the falacy of trying to do things...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2009 at 10:30 pm
Please don't bring the nightmare of inheritence anywhere near an RDBMS. 😉 And I don't care if SQL isn't up to speed when compared to GUI languages... they're simply...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2009 at 10:23 pm
Thank you for taking the time to post the test data the way you did... saves me a lot of time...
This will do it...
;
WITH
ctePreAgg AS
(
SELECT Name1,
...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2009 at 10:17 pm
*********************************************************
** Here you are setting the variable @SqlSelect and then padding it with 10 additional characters
*********************************************************
--===== Create the SELECT part of our dynamic SQL
SELECT @SqlSelect = 'SELECT d3.Tag,' + CHAR(10)
Good...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2009 at 10:02 pm
Viewing 15 posts - 40,756 through 40,770 (of 59,070 total)