May 13, 2010 at 5:09 pm
kazim.raza (5/13/2010)
Lol... So far so good.. both the design and our 'friend' 😛I want to discuss that with you... how about if get you the schema of our data mart? Are you willing to brainstorm on it with me?
~ Kazim Raza
That sounds like a fair bit of time would be involved. I don't mind answering a couple of questions but I'd prefer it if this thread didn't turn into a full time job. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
May 14, 2010 at 6:55 pm
Certainly not; or else; what will our friend do 😛
By brainstorming I meant just to take a high level review or opinion...
~ Kazim Raza
May 15, 2010 at 10:20 am
kazim.raza (5/14/2010)
Certainly not; or else; what will our friend do 😛By brainstorming I meant just to take a high level review or opinion...
~ Kazim Raza
You should know me by now... I don't have a problem with that. And whether or not something is done correctly in my opinion, it's always good to see other ways of doing things.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2010 at 10:34 am
The CTE was introduced into standard SQL in order to simplify various classes of SQL Queries for which a derived table just wasn't suitable. For some reason, it can be difficult to grasp the techniques of using it. Well, that's before Rob Sheldon explained it all so clearly for us.
"
May 16, 2010 at 11:53 am
aabrar.jnu (5/16/2010)
The CTE was introduced into standard SQL in order to simplify various classes of SQL Queries for which a derived table just wasn't suitable. For some reason, it can be difficult to grasp the techniques of using it. Well, that's before Rob Sheldon explained it all so clearly for us."
It's not the CTE that's the problem here. Kazim has a handle on that. It's what the CTE is being used for that's the problem...
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 5 posts - 61 through 64 (of 64 total)
You must be logged in to reply to this topic. Login to reply