Viewing 15 posts - 49,456 through 49,470 (of 59,091 total)
New Commer (7/3/2008)
i have a query like this,
Select Distinct Table1.name, Table1.Code, Table2.Place, Table2.Marks From Table1 inner join Table2 on Table1.code = Table2.code
which results,
Name1/N1/Nagpur/114
Name1/N1/Nagpur/154
Name1/N1/Nagpur/123
i want it to display as
Name1/N1/Nagpur/114
...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2008 at 10:29 pm
Vijaya Kadiyala (7/3/2008)
hi,You can't implement this logic in DB side
I agree that formatting for display should, indeed, be done in the GUI.... BUT, gosh, you really need to be sure...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2008 at 10:25 pm
Heh... yeaup... we've all been there.
My problem is that I end up double and triple checking my query, find out that it's spot on, and that someone really did screw...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2008 at 9:59 pm
Tim OPry (4/17/2008)
I did think he made several interesting points and would be interested in what some of you think:
My personal feeling is that Tony just doesn't like writing stored...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2008 at 9:53 pm
Peter Schofield (7/3/2008)
Stored procedures in SQL Server are the primary way to go for data access & manipulation for performance, security, and modularity.
That's a great thing to say... but, even...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2008 at 9:40 pm
rbarryyoung (7/3/2008)
As for...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2008 at 9:34 pm
Matt Miller (7/3/2008)
but still - technically possible....
Maybe THAT'S where you should use a cursor! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2008 at 9:18 pm
GilaMonster (7/3/2008)
Phil Factor (7/3/2008)
I'm so pleased you got the recognition. I'm a great fan of your forum entries. I was trying to find my favourite one of all, in which...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2008 at 9:14 pm
... and we STILL need to know how often the data in the hierarchy will change... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2008 at 9:07 pm
Yep... that's what I use...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2008 at 9:01 pm
There are several ways and some depend on the condition of the data. The way with the most performance is Bulk Insert... I recommend you take a look at...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2008 at 9:47 am
Jeff Moden (7/3/2008)
Ted Pin (7/3/2008)
Oops, I meant "Would a prolific contributor like to write [a guide to writing articles] for [the SQLServerCentral.com community]?"
Nah... I'd get it wrong... I think I...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2008 at 9:35 am
JJ B (7/3/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2008 at 9:29 am
Ted Pin (7/3/2008)
Oops, I meant "Would a prolific contributor like to write [a guide to writing articles] for [the SQLServerCentral.com community]?"
Nah... I'd get it wrong... I think I need to...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2008 at 9:10 am
Peter E. Kierstead (7/3/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2008 at 8:59 am
Viewing 15 posts - 49,456 through 49,470 (of 59,091 total)