Viewing 15 posts - 41,806 through 41,820 (of 59,067 total)
First... sorry... I meant "Elliot"... not "Lowell". I've been looking at a lot of his posts.
I agree with you if there's no "User" table other than the WebUser table.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 22, 2009 at 7:17 pm
Lynn Pettis (9/22/2009)
declare @Date1 datetime,
@Date2 datetime;
set @Date1 = '2009-09-22 12:20:21.333';
set @Date2 = '2009-09-22 12:20:21.000';
select
...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 22, 2009 at 7:09 pm
Lowell's idea is good in that it leads to a more normalized database... which I absolutely agree with. To wit, the UserName column should be removed from the WebUser...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 22, 2009 at 7:04 pm
If it's only one table, you could create a VIEW. If it's a whole bunch of tables for something like a reporting server and you have a SAN, you...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 22, 2009 at 6:56 pm
arun.sas (9/22/2009)
Use the UNION to get correct result.
Ummmm... maybe not... UNION will get rid of any duplicates and the duplicates may be important.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 22, 2009 at 6:33 pm
SSSolice (9/22/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 22, 2009 at 6:20 pm
adam spencer (9/22/2009)
BOL wont help me either.
I looked it up in SQL Server 2005 Books Online... all of the parameters are explained as well as what the what is contained...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 22, 2009 at 6:15 pm
Bill-89778 (9/22/2009)
This is a link to an article that desribes a method for custom grouping and subtotaling.http://www.simple-talk.com/sql/reporting-services/reporting-at-the-top/
It may be flexible enough for your requirements...
Bill
Ummm... can someone tell me what's...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 22, 2009 at 5:58 pm
Steve, you and Nelson are absolutely spot on. I'll add one more important reason to network and it's the diametric opposite to what most people think... it helps you...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 22, 2009 at 5:47 pm
David Kranes (9/22/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 22, 2009 at 5:38 pm
I'm not much into SSIS but my first dash at this would be to drop the package and rebuild it. It wouldn't be the first time I ever saw...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 22, 2009 at 5:34 pm
Just so that more than one voice is heard on this... I agree with Mhlewis on this. An outer join to a Calendar table or a derived table genned...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 22, 2009 at 5:28 pm
As a side bar... this is why I cringe at the idea that 2k8 actually has separate datatypes for date only and time only. Everyone is going to start...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 22, 2009 at 5:23 pm
Since I've worked on both, I can give you some very good tips...
Step 1. Relax... SQL Server doesn't require things like Reference Cursors to return a result set....
--Jeff Moden
Change is inevitable... Change for the better is not.
September 22, 2009 at 5:16 pm
I'm not quite sure what you mean... do you mean you want to make a copy of the table AND the data?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 22, 2009 at 5:09 pm
Viewing 15 posts - 41,806 through 41,820 (of 59,067 total)