Viewing 15 posts - 45,991 through 46,005 (of 59,101 total)
How odd... here we're talking about portability between releases of SQL Server... the ANSI-only folks would have a ball with this. Of course, then I'd have to launch some...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2009 at 6:13 am
Grant Fritchey (1/13/2009)
Jack Corbett (1/12/2009)
Sergiy (5/28/2007)
If you don't specify the version that means it must work on EVERY version, not only the one you know.
Of course these means that CTE's...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 13, 2009 at 6:09 am
GilaMonster (1/12/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 12, 2009 at 1:28 pm
Steve Jones - Editor (1/12/2009)
case
when substring( namefield, 1, charindex(' ', namefield) = 'Mr'
then prefix = 'Mr'
when substring( namefield, 1,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 12, 2009 at 1:26 pm
GSquared (1/12/2009)
Agree with you on most points.I like the Inner Join syntax. Makes it easier for me to read (not for you, but it does for me).
That would...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 12, 2009 at 1:14 pm
Sergei Ely (1/12/2009)
John,The code worked perfectly. 😀 Thanks again.
Sergei
Heh... actually, it's "Jeff" but I appreciate the feedback anyway. Thanks, Sergei. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
January 12, 2009 at 12:48 pm
On the other hand, Backups and Restores work very well for individual databases and also allows for a multi-server environment which has both it's own pains and advantages.
The bottom line...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 12, 2009 at 9:57 am
gvsriramakrishna (1/11/2009)
Oops.. there seems to be an error in th SQL query at the over keyword.Incorrect syntax near the keyword 'OVER'.
No... I wanted to know how the UPDATE solution works....
--Jeff Moden
Change is inevitable... Change for the better is not.
January 12, 2009 at 6:32 am
Grant Fritchey (1/11/2009)
I just remember seeing the solution in his book. It's not something I played with a lot myself, mainly because I long stopped worrying about gaps...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 12, 2009 at 6:24 am
Hmmmm... is there a way for you to turn of the hyperthreading long enough to run another MAXDOP 1 test? I've got a feeling and would like to find...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 11, 2009 at 9:18 am
Was it ever fast? If so, what changed? If not, then it's probably the code.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2009 at 11:46 pm
There are way too many variations of how a name may be entered to write some "simple" SQL for this. Instead of trying to reinvent the wheel, why don't...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2009 at 11:38 pm
majorbloodnock (1/8/2009)
I can just see the new posts being typed right now
"Dear SSC
Plz tell me what makes a good DBA and what else I need to know to become...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2009 at 11:35 pm
Yogi Berra had a saying... "When you come to a fork in the road, take it!" In other words, given a choice, take all choices.
A partitioned table would work...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2009 at 11:26 pm
Heh... nah... I just hate GUI's... too limiting... can only do what they were designed to do using only the ways they were designed to do it... unless you write...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2009 at 11:02 pm
Viewing 15 posts - 45,991 through 46,005 (of 59,101 total)