Viewing 15 posts - 46,156 through 46,170 (of 59,095 total)
Just a followup folks... I tried the original cursor/While loop based function on my box... now, keep in mind that it doesn't produce the required output... it just creates a...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2009 at 12:03 pm
Phil Factor (1/3/2009)
My solution was almost identical, except that I did an explicit create for the temporary table. (I'm showing my age here; It used to lock system tables for...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2009 at 11:47 am
OK... here we go. First, I'm gonna recommend that you add the following index to the WebLogEvents table... it will NOT interfere with inserts or deletes, will not need...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2009 at 11:00 am
jacroberts (1/2/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2009 at 9:18 am
Matt Whitfield (1/2/2009)
Temp table version of the above, outside the scope of a functionExec time 3.843
Oh, now I know I need to upgrade my poor ol' 6 year old work...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 7:01 pm
talk2riya15 (1/1/2009)
Can you please tell me how to add columns dynamically in a table...like i have created one employee table with EmployeeId, Name Passpost No,Permanent addresss....i want to add...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 5:49 pm
Stephanie J Brown (1/1/2009)
But I love books...
I'm with you there... I never throw one away, either. I've got some old DOS 2.0 books with a trick in them here...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 5:41 pm
santosh.shrestha (1/1/2009)
Sorry about my ignorance.The solution query is as follow:
SELECT Item, Name, COUNT(Amt), MIN (Amt), MAX(Amt), MIN (Date), MAX (Date) FROM Table1 GROUP BY Name, Item
Thanks again.
Cool... Thanks, Santosh. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 5:38 pm
Chris Morris (1/2/2009)
It's always nice to have some proof...and here it is...
Very, [font="Arial Black"]very [/font]well done... there's absolutely no argument when the arguments offered are in the form of viable,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 5:28 pm
If there's nothing in the file that violates either privacy or policy, my recommendation would be to attach the file to a post and let us take a crack at...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 5:10 pm
aziz.kapadia (12/31/2008)
Can I declare table variable as output parameter in stored procedure?
Probably of more importance, what is it that you're trying to do? You'll be amazed at the possible...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 5:06 pm
Grant Fritchey (12/31/2008)
Thanks for the correction. I wasn't sure and I haven't really looked at the table valued parameters yet. I should have kept my mouth shut.
Heh... nope... then I...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 5:04 pm
So! You carry the cell phone to the barn... when ya goin' for the implant, pal? ;):D:hehe:
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 4:08 pm
Good golly... I'm glad I'm not the only one that believes in the usage of well formed and safe dynamic SQL. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 3:56 pm
NULL (1/2/2009)
DECLARE @Tour TABLE (tourID INT IDENTITY PRIMARY KEY
,tourName VARCHAR(50)...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2009 at 3:35 pm
Viewing 15 posts - 46,156 through 46,170 (of 59,095 total)