November 30, 2010 at 10:06 pm
CirquedeSQLeil (11/30/2010)
For any that might be interested in an opportunity to heckle a threadizen, check this out[/url].
Very cool... looking forward to that.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 30, 2010 at 10:08 pm
Jeff Moden (11/30/2010)
CirquedeSQLeil (11/30/2010)
For any that might be interested in an opportunity to heckle a threadizen, check this out[/url].Very cool... looking forward to that.
Put it on the calendar and we will hope to see you there.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 1, 2010 at 12:31 am
December 1, 2010 at 2:20 am
GilaMonster (11/30/2010)
GSquared (11/30/2010)
If it were written:
SELECT ..
FROM T1
inner join T2
on T1.a >= T2.b
inner join T3
on T1.a <= T3.c;
Would you still question it? It's the same query, but it looks "more usual".
Yes, I would. There'd have to be a really good reason for a query to need two triangular joins (and nothing else). It has the smell of someone trying to be 'smart' and 'clever' with database design.
Yeah, there are likely legit reasons for this, but not common ones.
It would make plenty of sense if T2 and T3 were control tables with very few rows. Ideally one row each, but then you'd want all of that row in one table 😉
For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden
December 1, 2010 at 2:21 am
WayneS (11/30/2010)
To all the Threadizens that have presented - how have you incorporated this public speaking into your resume? Examples would be great!
Good Lord Wayne you're morphing into Karthik :unsure:
For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden
December 1, 2010 at 2:25 am
Jeff Moden (11/30/2010)
Grant Fritchey (11/30/2010)
Jeff Moden (11/30/2010)
Changing subjects, have you seen today's featured script? It comes under the category of "Are the featured scripts getting worse"? I try to be tolerant but some of these folks just don't have a clue. I believe I'm going to break out some polite but very high velocity pork chops later on tonight. Here's the link to the script. I find it difficult to believe that anyone gave it a rating of higher than 1.http://www.sqlservercentral.com/scripts/String+Manipulation/71602/
The scary thing for me is, like some of the more... questionable, articles, these things get high ratings. This one is only at 2.5 stars, but it's at 2.5 stars.
Even worse, it started out at 5 stars this morning and if you look at the first several posts in the discussion, several people are throwing accolades at the author for posting such "good" code.
It must be obvious to most threadizens by now that an element of national pride sometimes takes precedence over code quality.
For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden
December 1, 2010 at 4:33 am
WayneS (11/30/2010)
To all the Threadizens that have presented - how have you incorporated this public speaking into your resume? Examples would be great!
I'd put it under the Freelance Consultant part of my resume. Public speaking = teaching. So phrase it that you taught Y subject to X number of students. It's true and if they question it, you can give more details. Don't say "it's just public speaking." You're teaching a subject, even though you did it voluntarily. You had students.
December 1, 2010 at 4:40 am
GilaMonster (11/30/2010)
GSquared (11/30/2010)
If it were written:
SELECT ..
FROM T1
inner join T2
on T1.a >= T2.b
inner join T3
on T1.a <= T3.c;
Would you still question it? It's the same query, but it looks "more usual".
Yes, I would. There'd have to be a really good reason for a query to need two triangular joins (and nothing else). It has the smell of someone trying to be 'smart' and 'clever' with database design.
Yeah, there are likely legit reasons for this, but not common ones.
Actuarial math requires triangles. A VP at my workplace uses triangles regularly for predicting and estimating future behavior. So I can see an instance where this might be useful in my work place.
Additionally, for non-actuarial purposes... Orders table (t1), Pending Orders (t2), Fulfilled Orders (t3). The orders table contains all orders. Pending Orders tracks those orders that have been received but not packaged or shipped. Fulfilled Orders is a table that tracks shipped orders. So to find the orders that aren't in either table (perhaps the packaged, but not yet shipped orders), you could use a JOIN like that.
Okay. Maybe that one is reaching a little. But what about a versioned data warehouse situation?
December 1, 2010 at 5:08 am
December 1, 2010 at 5:15 am
Tom.Thomson (12/1/2010)
CirquedeSQLeil (11/30/2010)
For any that might be interested in an opportunity to heckle a threadizen, check this out[/url].The 744 pixel wide image doesn't really fit well unscaled in a 670 pixel wide slot.
I had the same problem. I don't even know what the meeting's about because I couldn't read it.
December 1, 2010 at 5:17 am
WayneS (11/30/2010)
To all the Threadizens that have presented - how have you incorporated this public speaking into your resume? Examples would be great!
Oooh, good question. I haven't. I have listed my books & MVP status in a section I called "Other Interests and Qualifications"
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 1, 2010 at 5:48 am
Brandie Tarvin (12/1/2010)
Tom.Thomson (12/1/2010)
CirquedeSQLeil (11/30/2010)
For any that might be interested in an opportunity to heckle a threadizen, check this out[/url].The 744 pixel wide image doesn't really fit well unscaled in a 670 pixel wide slot.
I had the same problem. I don't even know what the meeting's about because I couldn't read it.
Oh, you can just right-click on the image and select "look at the image on its own" on the menu (not sure of the exact phrasing - my browser menus aren't in English - but that's what it means). Then you will get the whole image.
Tom
December 1, 2010 at 6:11 am
You know there's a problem when...
In the last 2 weeks there have been three resignations at current client:
The senior developer (leaving only 2 permanent developers)
The Chief Enterprise Architect
The CIO
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 1, 2010 at 6:12 am
Brandie Tarvin (12/1/2010)
GilaMonster (11/30/2010)
GSquared (11/30/2010)
If it were written:
SELECT ..
FROM T1
inner join T2
on T1.a >= T2.b
inner join T3
on T1.a <= T3.c;
Would you still question it? It's the same query, but it looks "more usual".
Yes, I would. There'd have to be a really good reason for a query to need two triangular joins (and nothing else). It has the smell of someone trying to be 'smart' and 'clever' with database design.
Yeah, there are likely legit reasons for this, but not common ones.
Actuarial math requires triangles. A VP at my workplace uses triangles regularly for predicting and estimating future behavior. So I can see an instance where this might be useful in my work place.
Additionally, for non-actuarial purposes... Orders table (t1), Pending Orders (t2), Fulfilled Orders (t3). The orders table contains all orders. Pending Orders tracks those orders that have been received but not packaged or shipped. Fulfilled Orders is a table that tracks shipped orders. So to find the orders that aren't in either table (perhaps the packaged, but not yet shipped orders), you could use a JOIN like that.
Okay. Maybe that one is reaching a little. But what about a versioned data warehouse situation?
That would seem an order or line status would be better suited and more scalable.
This could be in 1 table.
For the data warehouse - are you implying slowly changing dimensions?
Although the 3 tables wouldn't seem necessary.
Greg E
December 1, 2010 at 6:16 am
GilaMonster (12/1/2010)
You know there's a problem when...In the last 2 weeks there have been three resignations at current client:
The senior developer (leaving only 2 permanent developers)
The Chief Enterprise Architect
The CIO
Hey Gail, apply for the CIO position, then they'd have to listen to you!
<ducks and runs>
Viewing 15 posts - 22,021 through 22,035 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply