Viewing 15 posts - 58,381 through 58,395 (of 59,099 total)
http://forums.belution.com/en/sql/000/110/02.shtml
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2006 at 7:14 pm
Very nice...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2006 at 7:06 pm
That's cool...
You can also use NEWID() as the seed for Rand... in the algo below, "RANGE" is how many numbers you want in the range of random numbers and "OFFSET"...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2006 at 5:11 pm
Here's a self standing sample that you may run with impunity...
This turned out to be a bit long winded because an ORDER BY in an UPDATE in the presence of...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2006 at 2:13 am
FROM #YourTable y,
dbo.Tally t
Ok... now I'm confused
That is a Tally table in your code, isn't it?
Althought the Jury is still out...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 10, 2006 at 9:06 pm
Thanks for the great feedback, Kenneth. Yep... I know the double barreled last names need some help but James insists that they will all be hyphenated... I sure hope he's...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 9, 2006 at 8:05 pm
Thanks for the feedback, James.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 8, 2006 at 7:18 pm
Now there's an idea... thanks for pitching in...
hadn't thought about that approach.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2006 at 4:38 pm
If the first column is unquoted data, then the first column BCP would actually import a column (instead of "0" as the target column #) and you would, of course,...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2006 at 4:09 pm
Haven't tried it in Enterprise Manager... works fine in Query Analyzer...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2006 at 5:09 am
Yep, I agree with Kory...
Also, I believe that moving the reference to constants out of the ON clauses and into a WHERE clause will help a bit...
The other thing may...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2006 at 6:38 pm
Hilight the character, copy it, and paste it into the 'X' below in QUERY ANALYZER... it'll tell you what the character number is...
SELECT ASCII('X')
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2006 at 6:28 pm
Or...
SELECT REPLACE(STR(3,2),' ','0')
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2006 at 6:24 pm
He did say that is was for fun --Jeff Moden Change is inevitable... Change for the better is not.
and it does work for what James posted as a very limited original format
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
March 6, 2006 at 5:25 pm
Yep, I agree...
if you need to fumble with fill factors for all tables, then you are correct... hopefully, though, you let the default fill...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 6, 2006 at 4:45 pm
Viewing 15 posts - 58,381 through 58,395 (of 59,099 total)