Viewing 15 posts - 57,346 through 57,360 (of 59,101 total)
If you don't already have one... now is the time to make a "Tally" table... Here's how...
--===== Create and populate the Tally table on the fly
SELECT TOP 11000...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2006 at 7:49 am
Or... Use OSQL with the -h-1 option. Don't forget to set the -s option to a tab... you can't do THAT from the command prompt... you will need to make...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2006 at 7:30 am
Not sure Michael is set on this... FULL joins return all rows from both tables 1 time, Cross joins will produce either a partial or full cartesian join (ex. if...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2006 at 6:59 am
Bingo!... Nice job, CK...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2006 at 6:07 pm
Matti and John... you guys are "spot on" about temp tables. John, I absolutely agree... lot's of times, a good set based solution will require NO temporal structure whatsoever.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2006 at 6:05 pm
Correct... large table variables are NOT converted to temp tables...
I strongly recommend AGAINST using table variables for anything more than a dozen or so rows because they cannot be...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2006 at 6:03 pm
I strongly recommend AGAINST using table variables for anything more than a dozen or so rows because they cannot be made to use statistics... both table variables and temp tables...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2006 at 5:57 pm
Outstanding... thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2006 at 5:23 pm
Very cool, David... fast as all get out... but try this... obviously, we have to know exactly what the scale of the decimal places is to use it or we...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2006 at 5:20 pm
>>But there are cases where a cursor is necessary.
I would agree... BUT, the problem is most people don't really know where that...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2006 at 7:18 am
It'll take me a bit to setup some test data and write an example (an I'm going to bed for the night so not happening tonight), but I'm thinking a...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2006 at 10:30 pm
John is spot on...
I'll also add that storing text columns in the database is bad for too many reasons to post here. If you must store text that execeeds...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2006 at 10:21 pm
Lynn is absolutely correct... for those that can't find the ROUND function in Books Online
here's what the 3rd operand of "1" means...
function
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2006 at 10:17 pm
Spot on, Robert!
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2006 at 10:13 pm
As an alternative, check out sp_WHO in Books Online and it's undocumented cousin sp_WHO2.
Also, I haven't check how @@PROCID reacts in a trigger but it might be another simple...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 25, 2006 at 10:03 pm
Viewing 15 posts - 57,346 through 57,360 (of 59,101 total)