Viewing 15 posts - 50,386 through 50,400 (of 59,099 total)
15 table join with a non-indexable WHERE clause and a killer ORDER BY and we wonder why this code takes a bit to run? First thing to do would...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 7:16 pm
I think an ALTER instead of a DROP would probably work faster.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 7:10 pm
Yes... the INSERT/EXEC would be used to save the results in a table. If you get different results, use more than 1 table... nothing wrong with that.
Of course, you...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 7:07 pm
David Burrows (5/21/2008)
Keep think about submitting something but can't think of anything that ain't already been done 🙁
Actually.... everything I've written about is NOT new... Tally table is old...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 6:50 pm
On the truncation problem, everyone realizes that the table columns must be in the same cardinal order as the input file unless you use a format file, right?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 6:09 pm
Do you mean "ISO Standard"?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 6:06 pm
Consistency didn't stop 20 inch wheels from coming out nor has it prevented the use of 13" wheels on some small cars.
Whatever... we could go on forever... our ideas of...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 5:27 pm
ntaylor (5/21/2008)
Jeff Moden (5/21/2008)
Properly done, written enforced standards won't prevent someone from trying something new,
Again, though. How do you measure when it's being properly done? You can easily measure...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 4:35 pm
Don't need Q1 ... nothing to join it to Q2 with.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 4:13 pm
Properly done, written enforced standards won't prevent someone from trying something new, but a process outside the standards should be approved for use. For example, we have a standard...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 9:10 am
While researching this, I found out that the default replication process is to split it up into multiple single-row inserts. This behavior is a problem for us. Instead...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 8:38 am
Heh... see what I mean? Couple hours went by for the original post... 10 minutes after the working table and data was posted in executable form, WHAM! Two...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 8:22 am
Not a problem... but you really have to get in the habit of making things easy on me... post the Create Table statement and the Insert/Select/Union All's that are requried...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 8:18 am
Nice and simple, pleasure to read. Well done, John! 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 8:07 am
I'd bust up the query and store interim answers in a Temp Table instead of doing such a large group by... especially since the GROUP BY is to support 1...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2008 at 10:28 pm
Viewing 15 posts - 50,386 through 50,400 (of 59,099 total)