Viewing 15 posts - 40,936 through 40,950 (of 59,102 total)
This should get you started...
WITH
cteRandomlyNumber AS
(
SELECT PersonID,
CoID,
RowNum = ROW_NUMBER() OVER (PARTITION BY...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 8:49 pm
Ummmm.... I haven't used them in SQL Server but wouldn't synonymns do the trick here?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 8:36 pm
If you forget to put gas in the boat, "RBAR" (Row-By-Agonizing-Row) may actually mean something.... heh... Oar Not... 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 8:34 pm
mister.magoo (11/26/2009)
...wanted to offer an alternative that requires no user input beyond the initial running of the script....(I like not having to think)
How did the ol' Magoo cartoons always end?...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 7:11 pm
I'm glad to see a kindred spirit out there, Noel. Thanks for the cheer-me-up. Your post is a big breath of fresh air. Thank you, Sir. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 6:49 pm
Paul White (11/29/2009)
C# Screw (11/29/2009)
Oh but if I switch current database from Master to 'Another' database I get very differerent results...
The collation thing again. It'd probably be fairer to...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 6:05 pm
The collation and sort order would certainly explain the performance differences. All of mine (including Master and TempDB) are setup using the installation default of SQL_Latin1_General_CP1_CI_AS. You might...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 5:40 pm
C# Screw (11/29/2009)
Oh but if I switch current database from Master to 'Another' database I get very differerent results:
Ah ha... I wonder how many other folks have the default DB...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 11:14 am
C# Screw (11/27/2009)
Must be some hardware having influence on this, or is this being affected by collation..Pro Duo, 2gb ram, 700MB free, SQL 2005
Looks like I didn't lose the code...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2009 at 11:08 am
C# Screw (11/25/2009)
would you think the HasSpace is finally getting rid of the RBAR? - I am thinking this because this is the only solution where SQL can use...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2009 at 11:51 am
It has been fun to say the least, Barry. And, I'll always refer to you whenever I hear the term "Pseudo-Cursor" because you're the first one I heard it...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2009 at 11:37 am
I can't get it to fail with any of the data you've provided. Then only thing that I can think of is...
1) Maybe you're providing the wrong line of...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2009 at 11:34 am
xponcall (11/27/2009)
The reason for this report and data present this way are for account department audit analysis, which have keep the track of the inventory flow in and...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2009 at 11:29 am
You miss the point I was trying to make... why do you have both an input and an output ProdID and Qty? What are the rules for what goes...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 27, 2009 at 12:17 pm
Actually, the rewrite is out there now...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 27, 2009 at 12:09 pm
Viewing 15 posts - 40,936 through 40,950 (of 59,102 total)