Viewing 15 posts - 59,056 through 59,070 (of 59,075 total)
Using Jonathon's example...
SELECT DISTINCT a.Col + b.Col
FROM Table a JOIN Table b ON a.Col <= b.Col
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2004 at 8:44 pm
Before it get's much more complicated, perhaps you should look into OLAP Services which comes free with MS-SQL... OLAP (online analytical processing) is on of the "other" things on your...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2004 at 8:35 pm
Thanks carimines... ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
March 5, 2004 at 6:51 am
--Jeff Moden
Change is inevitable... Change for the better is not.
March 4, 2004 at 9:59 pm
All well and good...
But the "poster" said that he wanted to do this as a VIEW!
I asked the question a while back, "How...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2004 at 5:28 pm
pbaldy,
Would you mind sharing what you did?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2004 at 9:21 pm
>I would like to do this in a view if possible becuase it is going to be used as the data source to a report designer.
How would you pass a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2004 at 9:19 pm
set @db =
(select TOP 1 Name from dbo.sysdatabases
where name like 'CCM%'
order by crdate DESC )
EXEC ('USE '+ @db
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2004 at 8:47 pm
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2004 at 8:35 pm
noeld had it right but swapped the @StartDate and @EndDate... his SELECT statment should have looked like this and THEN you would probably have the correct answer...
select Convert(varchar(5), @ENDDate -...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2004 at 9:08 pm
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2004 at 9:01 pm
First, thanks for pointing out the difference there, Butch. Guess I better get some glasses! ![]()
And, thank you pnewhart, for pointing out just exactly...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 1, 2004 at 8:48 pm
Maybe it's just me and I really am going blind... would someone tell me what the difference is between the two lines that pnewhart put in his last post? --Jeff Moden Change is inevitable... Change for the better is not.
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
February 28, 2004 at 12:47 pm
My experience has been that 2 DELETE queries will run much faster than a single query with a BOOLEAN "OR". Also, even with the "SIMPLE" recovery method set, the deletes...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 25, 2004 at 8:52 pm
As I alluded to in my original posting...
Casting (or Converting) the date as INT or BIGINT may give you the wrong
(next day)...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 25, 2004 at 8:29 pm
Viewing 15 posts - 59,056 through 59,070 (of 59,075 total)