Viewing 15 posts - 35,296 through 35,310 (of 59,099 total)
Thanks for posting the code.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2011 at 8:07 pm
CELKO (1/19/2011)
(i INTEGER NOT NULL PRIMARY KEY);
WITH Sequenced_Foobar (i, seq)
AS
(SELECT i, ROW_NUMBER() OVER(ORDER BY i))
SELECT S1.i, S2.i
FROM Sequenced_Foobar AS S1
...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2011 at 7:17 pm
Koen (da-zero) (1/19/2011)
WayneS (1/19/2011)
This thread has made me realize that I suck in deciphering job descriptions. Craig, hurry up with your articles - I need the help!!!
At my place, job...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2011 at 6:49 pm
GilaMonster (1/20/2011)
Ferguson (1/20/2011)
Where I continue to resist however is the whole generalist idea. They must be out there.
Sure they are. However you've indicated you want hotshots. Top skills....
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2011 at 6:29 pm
Thanks Gus.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2011 at 1:42 pm
marcin.motyl (1/20/2011)
I think, that my test environment is far weaker;).
Forgive me, but I will...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2011 at 1:25 pm
nandakrishnacherukuri (1/19/2011)
Thanks For giving the solution.
You're welcome but, I need to make sure, do you understand the solution? If you don't, don't use the solution because you'll need to...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2011 at 1:23 pm
allmhuran (1/20/2011)
"You mean an 8% increase in performance with 44% less typing? Don't you wish you could do that everywhere?"SOLD!
Heh... I agree! Thanks for stopping by. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2011 at 8:37 am
Phil Factor (1/20/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2011 at 8:35 am
sharath.chalamgari (1/20/2011)
Thanks Jeff for the article. i learned something about the datename function and these langauages settings.
Thanks for the feedback Sharath. As so often is the case, I...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2011 at 8:33 am
radyo (1/20/2011)
/*------------------------
DECLARE @BitBucket CHAR(4);
PRINT '========== DATENAME Method of Conversion ==========';
SET...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2011 at 8:27 am
Koen (da-zero) (1/20/2011)
Whupty-freakin'-doo! This is an amazing article!I have never heard of DATENAME before, so thanks for pointing it out Jeff.
You bet Koen... thanks for the feedback.
As a side bar,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2011 at 8:22 am
katesl (1/20/2011)
I have to ask this question because I have no experience doing user interface programming-- I use T-SQL and SSMS, and Excel to deliver reports, for...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2011 at 8:19 am
carie dobson (1/20/2011)
I've been using SqlSvr since the 6.5 days I still learn new stuff everyday. I have to admit I usually use...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2011 at 8:16 am
alen teplitsky (1/20/2011)
is this a SQL 2008 only function or is it in SQL 2005 as well?
I believe that it'll work in any version of Standard or Enterprise editions. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 20, 2011 at 8:15 am
Viewing 15 posts - 35,296 through 35,310 (of 59,099 total)