Viewing 15 posts - 27,586 through 27,600 (of 59,101 total)
David.Poole (2/1/2013)
@jeff, it sounds as if you should write a counterpoint article for EAV.
I kind of did already.
http://www.sqlservercentral.com/articles/T-SQL/63681/
http://www.sqlservercentral.com/articles/Crosstab/65048/
Admittedly, they're at the 100 level but they provide a decent start to...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2013 at 6:42 pm
Kasinathan (2/1/2013)
Hi i need to calculate the TAT in my application.
Heh... I hate to ask. What's a "TAT"?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2013 at 6:35 pm
I have to ask. If you're using SQL Server 2008, why do you insist on using OPENXML?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2013 at 6:29 pm
30 rows on a table variable isn't enough for a performance test but I do like your second solution, Lynn.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 1, 2013 at 6:02 pm
Lynn Pettis (1/31/2013)
Question for those...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 31, 2013 at 11:32 pm
jasona.work (1/31/2013)
Jeff Moden (1/30/2013)Detroit? Do you attend the local PASS meetings? Do I know you and am just missing the connection?
I've not (yet) attended any of the local...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 31, 2013 at 11:27 pm
What about TempDB, an archive, and a spare? 10 Drives doesn't seem to be enough even if TempDB is on DAS (which would mess with clustering if you went...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 31, 2013 at 7:40 pm
David.Poole (1/31/2013)
@jeff What sort of size, scale and traffic are you putting through your EAV models?
Some of the tables got quite large (several million rows). The post just...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 31, 2013 at 5:27 pm
BillyJack (1/31/2013)
Jeff Moden (1/30/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 31, 2013 at 12:08 pm
jasona.work (1/30/2013)
Chad Crawford (1/30/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2013 at 4:22 pm
Mr. Kapsicum (1/30/2013)
SELECT * FROM TBLCOLOR
WHERE COALESCE (COLOR, '') = COALESCE (@COLOR, COLOR, '');
in this query coalesce(@color,color,'')
the field color is always not null then how can we compare ''.?
and...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2013 at 8:29 am
Actually, for the data given, the correct answer is 29 because of project 4.
SELECT Total = SUM(d.Qty)
FROM (
...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2013 at 8:24 am
I'm one of "those" people that kept saying that there were a million articles on how to determine if corruption had occurred and very few on what to do about...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2013 at 7:47 am
lnardozi 61862 (1/29/2013)
Now I'm really curious. What does changing a table structure have to do with SQL programming skills?
--Jeff Moden
I'm sure you've seen this hundreds of times before - you're...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2013 at 7:06 am
BillyJack (1/29/2013)
Jeff Moden (1/28/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2013 at 6:44 am
Viewing 15 posts - 27,586 through 27,600 (of 59,101 total)