Viewing 15 posts - 46,456 through 46,470 (of 59,095 total)
Santhosh (12/23/2008)
vbandlamudi (12/23/2008)
Correct Answer
Select id,name, sal, cumsal=
(select sum(t1.sal)
from employee_san t1
where t1.id <= t.id)
from employee_san t
This works fine.
But the salary is not ORDERed BY ASC
It works fine for only...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 23, 2008 at 5:04 am
vbandlamudi (12/23/2008)
Correct AnswerSelect id,name, sal, cumsal=
(select sum(t1.sal)
from employee_san t1
where t1.id <= t.id)
from employee_san t
Ummmm... No... that's NOT the correct answer. That makes a triangular join. Try...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 23, 2008 at 5:00 am
Heh... and it works so well for these types of bitwise ops.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2008 at 5:18 pm
Ya gotta love it when the ops cooperate.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2008 at 5:17 pm
jac (12/22/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2008 at 5:11 pm
Using Luke's good code example, you can label to "sum", as well...
--create test table
CREATE TABLE #test (
id INT,
amount MONEY)
--insert sample data
INSERT INTO [#test]
SELECT 1,10.00
UNION ALL
SELECT 1,20.00
UNION ALL
SELECT 2,10.00
SELECT CASE...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2008 at 4:38 pm
That's good advice if you're going to do something like that... but, most maintanence doesn't require a single connection like that. Not sure that's enough justification to give up...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2008 at 4:32 pm
kashifyaqoob (12/22/2008)
It is really helpfull for me. Thanks.
Be very careful.... anytime you find the need to update or insert your own numbers into an IDENTITY column, you're probably doing something...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2008 at 4:28 pm
Japie Botma (10/21/2005)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2008 at 4:26 pm
Um.... I don't know much about IIS, but I'm pretty sure that you're going to have to make a trip to OSQL via a command shell call.
The best thing to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2008 at 4:18 pm
Here's a real cheater method...
SELECT SIGN(SUM(Col1+0)), SIGN(SUM(Col2+0)), SIGN(SUM(Col3+0))
FROM SomeTable
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2008 at 4:08 pm
Not sure I spelled it right but...
"Gung hay fat choy"... happy new year!
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2008 at 3:54 pm
Also, if the code really isn't "proprietary", post your procedureal code and let us have a go at it, eh?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2008 at 3:45 pm
Kit Brandner (12/22/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2008 at 3:39 pm
leonp (12/22/2008)
2. It has 7-8 processing steps for each of...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 22, 2008 at 3:21 pm
Viewing 15 posts - 46,456 through 46,470 (of 59,095 total)