Viewing 15 posts - 38,041 through 38,055 (of 59,072 total)
skcadavre (6/8/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 6:24 pm
Unless I'm missing something, this problem is impossible to solve because there's simply nothing to guarantee the order of the data. There has to be a date entered column...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 6:19 pm
Oleg Netchaev (6/7/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 6:07 pm
Mike Mullen (6/8/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 6:02 pm
Thanks for the plug, Stefan. :blush:
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 4:33 pm
Agreed and sorry Scott. I didn't word my post quite correctly.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 4:20 pm
Scott has it sussed above... almost everyone forgets that aggregations include MAX to handle character based cross tabs. The only thing you may want to (probably should) change in...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 4:06 pm
Just to confirm... SMALLDATETIME rounds at the 30 second mark. In the last 30 seconds of a given day, it will round up to the next minute which is...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 4:04 pm
WayneS and bteraberry... thanks for the great kudo. :blush:
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 3:58 pm
omri.wallach (6/8/2010)
Select
i.Amount as Balance
From
ARHeader h
join ARDetail d on h.Voucher = d.Voucher and h.CompCode = d.CompCode
join ARItem i on d.[LineNo] = i.[LineNo] and d.Voucher = i.Voucher
Where
i.CompCode='Will'...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 8, 2010 at 3:58 pm
Vivek29 (6/7/2010)
A table in sql server database is seems to be locked and is not accessible.I am executing Select statement, it keeps on running.
How to resolve this issue?
Thanks
Vivek
I agree with...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 7, 2010 at 5:16 pm
danderson 57106 (6/7/2010)
Reboot
Lordy, I hope you're not serious.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 7, 2010 at 5:13 pm
IMHO, it's not a 1:1 relationship if there are a lot of nulls.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 7, 2010 at 5:09 pm
Heh... can't cover the world... just one post at a time. And please don't think I'm picking on you. Despite how I sound (my "tone of voice" in...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 7, 2010 at 1:21 pm
There's a fly in the ointment, though... try this data...
declare @rangeTable table (start int, [end] int)
insert @rangeTable
(Start, [End])
select 1, 2 union all
select 3,...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 7, 2010 at 5:59 am
Viewing 15 posts - 38,041 through 38,055 (of 59,072 total)