Viewing 15 posts - 33,016 through 33,030 (of 59,099 total)
srinath.vanama (8/1/2011)
am facing a performance problem in one server like there are so many blockings are occured on the server which becomes SQL server is using more CPU memory...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2011 at 7:37 am
Ninja's_RGR'us (8/2/2011)
I always wait 24H before actually posting anything in case this is an exam or cert or late homework.
I was hoping for an...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2011 at 7:13 am
Same message, talktosivas... lots of people want and need help and lots of good people on the forums want to test their answer against some data before posting their coded...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2011 at 7:05 am
johnsonchase7 (8/1/2011)
CREATE TABLE #TEMP
(ID INT, VALUE INT)
INSERT INTO #TEMP
select 0, 21 union all
select 1, 98...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2011 at 6:58 am
Ninja's_RGR'us (8/2/2011)
Ignoring the <uselessly> complexe query by peso... so what did you come up with?
Ummm... did you miss it, Remi?
I tried the following but the group by makes it...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2011 at 6:49 am
Leo.Miller (8/1/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2011 at 6:34 am
Leo.Miller (8/1/2011)
Since an iTVF is typically only called once it would be much like Vijay's original solution with the case statement, it would just be moved to the iTVF.
Hmmm......
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2011 at 6:31 am
As a side bar, I think it's really cool that you have 2K8. I also think it's really cool that you've learned to use the "new" Insert/Values. But,...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2011 at 7:48 pm
Pagan DBA (8/1/2011)
-- Which is FASTER?
Do what any of us would do... TEST IT and see! 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2011 at 7:40 pm
Heh... Joe who? 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2011 at 7:37 pm
Leo.Miller (8/1/2011)
In line functions aren't actually compliled into the code, they are still external functions that need to be called.
I agree that's true about Scalar and mTVF's (multi-line Table Valued...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2011 at 6:56 pm
If you really want help, post the data in a readily consumable format. See the first link in my signature line below for how to do that correctly.
As a...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2011 at 6:52 pm
Buy a copy of the SQL Server Developer's Edition (which will run fine on most home machines without Window's Server) and practice on your own. Buy a book on...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2011 at 6:48 pm
opc.three (8/1/2011)
Somewhere along the line I think you zigged and I zagged.
BWAAA-HAAA!!! No... it's not you. I just went back and reread the original post and see that,...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2011 at 5:32 pm
HLogic (8/1/2011)
I have tested the HierarchyID and associated functions against Adjacency Lists using CTE's, Nested Sets (a la Celko) and Nested Intervals (Hazel's implemetation) and found it to be lacking...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2011 at 6:58 am
Viewing 15 posts - 33,016 through 33,030 (of 59,099 total)