Viewing 15 posts - 31,861 through 31,875 (of 59,099 total)
sjsubscribe (11/22/2011)
Jeff Moden (11/20/2011)
Post the CREATE TABLE statement for you table and any/all the indexes you may have on the table and I'll show you the "Quirky Update" method Cold...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2011 at 5:44 pm
Wow! My appologies. I lost track of this thread. Let me know if you still need help with this and I'll try to get to it before...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2011 at 5:24 pm
GilaMonster (11/24/2011)
Jeff Moden (11/24/2011)
perhaps some experimentation with blocking needs to be done with utility tables, such as the Tally Table.
Those kind of tables should be read-only in use (I don't...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2011 at 5:01 am
ben.mcintyre (11/24/2011)
Jeez Jeff, I knew you'd been doing Tally tables for a long time, but you wrote the article THAT long ago ?Talk about nativity ...
😀
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2011 at 5:09 pm
We should frame this post as one of the reasons to not double post. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2011 at 4:13 pm
Oh, shoot. My apologies. I lost track of this thread. Here's the solution given the file name pattern you posted. I hope I'm not too terribly...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2011 at 4:08 pm
It's pretty much as I stated... instead of formatting data, pass the data as the correct data type.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2011 at 3:13 pm
Sam Bendayan (11/21/2011)
select yr,
month,
member,
(select count(distinct code)
from #testtable t3
where t1.yr =...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2011 at 2:54 pm
Amy.G (10/19/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2011 at 2:49 pm
Appoligies for the late reply but I guess I'll have to agree to disagree with you, Jeff. In most cases, the number of rows directed to a temp table...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2011 at 2:44 pm
PaulB-TheOneAndOnly (11/22/2011)
All reporting should happen in a database other than OLTP either a "Reporting" database or a properly structured "Data Warehouse"
Although that's the general concensus, I've found many cases where...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2011 at 2:04 pm
My most sincere appologies for the late reply. Thank you very much for the feed back.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2011 at 2:01 pm
That would do it! Thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2011 at 9:43 am
Apologies for the very late reply but thank you very much for posting all the work you did on this.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2011 at 9:40 am
GilaMonster (11/5/2011)
Jeff Moden (11/4/2011)
bteraberry (11/3/2011)
I agree with G^2. I would rather error on the side of reducing reads over picking the "fastest" time unless it is really disproportionate.
I'd have...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 24, 2011 at 9:18 am
Viewing 15 posts - 31,861 through 31,875 (of 59,099 total)