Viewing 15 posts - 55,081 through 55,095 (of 59,098 total)
What... and miss out on all that high-class entertainment? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2007 at 4:16 pm
Duplicate records DO happen on staging tables used for preprocessing rows from third parties, especially telephone companies... Either a "UNIQUE WITH IGNORE DUPES" index must be used (comparitively very slow)...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2007 at 4:16 pm
Heh... you're right... wrong article... it was about "RAAS", not "RAC"...
You'r still nothing more than a spammer... I can't understand why you don't get your product evaluated on this site......
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2007 at 4:12 pm
This should do it nicely... classic cross-tab... you might be able to use SQL Server 2005 PIVOT as well... either way, it'll solve your slowdown because each row is only...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2007 at 8:33 am
Now... that's a bummer...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2007 at 8:16 am
Spot on, Vladan ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2007 at 8:12 am
Also, be aware that this method uses a "Triangular Join" which can get very slow if the "triangles" are allowed to get to any size... they can be hundreds of times...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2007 at 8:11 am
So, why not post how to make a "Numbers" table or provide the actual link? Aren't we a full service shop? ![]()
Venkat... here's how...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2007 at 8:05 am
Karthik,
I get it from your description... Can't work on it right now because I'm on the way to work, but I've got to ask...
Why doesn't "he" want these flattened out...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2007 at 8:01 am
The article was nice and simple... shows how to make and exec a proc that uses a table parameter.
What I'd like to know (and anyone can certainly answer) is why...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2007 at 7:44 am
Heh... more spam... at least the table example works, Rog... Saw the free code you guys posted for RAC and apparently a lot of the stuff doesn't work correctly...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2007 at 7:39 am
On a busy system, if it's a batch proc, wait 5 minutes after it's done, and it won't be cached any more.
On a busy system, if it's a GUI proc,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2007 at 11:00 pm
Somebody,
If I have a lot of candidates with good resumes all lined up, I'll ask some questions outside of what the job specifically requires as "tie-breakers".
For example... let's say I...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2007 at 10:44 pm
Have you tried sp_HelpLogins? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2007 at 9:27 pm
Subtracting 2 milliseconds from the date won't do it because dates have a 3.3 millisecond resolution.
And, instead of fooling around with the time for end date, why don't you...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2007 at 9:09 pm
Viewing 15 posts - 55,081 through 55,095 (of 59,098 total)