Viewing 15 posts - 33,916 through 33,930 (of 59,102 total)
kdford10 (4/20/2011)
Mickey Mouse4/20/201110001 ...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2011 at 6:27 pm
Dan, are you all set on this one or do you still need some help?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2011 at 6:20 pm
jitendra.padhiyar (5/3/2011)
What is fill factor ? Can anyone explain it with one example?
Craig's explanation is a good one. For more detail, I recommend looking up "page splits" in Books...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2011 at 6:15 pm
Hi i am a developer in sql server. can any one suggest me what i shall learn next for bright career
Actually, yes we can. 🙂 Post (or attach it...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2011 at 5:46 pm
roshanmaugustine (5/10/2011)
I have a table with columns
ProjectID ,YearofOperation WeekNo,PorjectParameterSchedule, ProjectParameterScope,ProjectParameterResources,ProjectParameterQuality
1 2011 18 2 10 5 18
1 2011 19 6 8 9 45
1 2011 20 9 10...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2011 at 5:26 pm
CELKO (5/12/2011)
AS
SELECT DISTINCT country_name,
CASE WHEN col_1 <= col_2 THEN col_1 ELSE col_2 END AS col_1,
...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2011 at 5:18 pm
TheSQLGuru (5/3/2011)
That is by far the biggest shortcoming SQL Server has IMNSHO.
Unless you count the fact that there is no split function, no function to generate sequential numbers or dates...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2011 at 5:14 pm
ChrisM@home (5/2/2011)
This is probably the simplest set-based solution.
Oh... be careful, Chris. Apologies for quibbling but a Recursive CTE isn't set-based. It's a form of hidden RBAR which can...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2011 at 5:01 pm
Ah... I finally get the irony of your post, Remi. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2011 at 4:53 pm
the_hichamus (5/15/2011)
This is my first time posting on this forum.
DECLARE @LoginG as uniqueidentifier = (select l.LoginGUID from login l inner join EmailQueue eq on eqo.OriginatingColumnValue = l.LoginID...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2011 at 4:50 pm
I would imagine for the very reason you quoted. I also believe that the classification has been around for a very long time and that you've just not noticed...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2011 at 4:47 pm
Ninja's_RGR'us (5/15/2011)
:w00t:What link is that Jeff?
Looks like you're catching up the backlog of e-mails or something... thread ended over 10 days ago!
Heh... Considering this OP has reposted the same question...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2011 at 4:34 pm
Tom.Thomson (5/15/2011)
Jeff Moden (5/14/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2011 at 4:22 pm
Tom.Thomson (5/15/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2011 at 3:46 pm
In the area of "are the posted articles getting worse"...
I realize that it's an older article but isn't the word "Automatic" and code with hard-coded dates a bit of an...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 15, 2011 at 12:23 pm
Viewing 15 posts - 33,916 through 33,930 (of 59,102 total)