Viewing 15 posts - 14,956 through 14,970 (of 59,097 total)
Yes. A "fact table" is a duplication of data that must be separately maintained. It would probably be better to create what is known as a "Partitioned View" and reference that...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 1, 2017 at 6:03 pm
I see a claim of working against 1.7 million rows. What does the data actually look like and what is the structure of the table that you're using for the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 1, 2017 at 5:39 pm
--Jeff Moden
Change is inevitable... Change for the better is not.
June 1, 2017 at 11:26 am
--Jeff Moden
Change is inevitable... Change for the better is not.
June 1, 2017 at 8:35 am
GilaMonster - Thursday, May 21, 2009 3:50 AM
Ian Scarlett (5/21/2009)
Why it doesn't work with a datetime2 must be down to the underlying datatypes Microsoft are using internally.
Datetime is...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 31, 2017 at 7:46 pm
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2017 at 3:02 pm
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2017 at 2:16 pm
Personally, I wouldn't use either. Use a TIME datatype. It'll save you on a huge number of conversion problems and implicit casts in the future.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2017 at 12:17 pm
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2017 at 11:09 am
I absolutely agree with Gail on ignoring the "fragmentation" you're seeing. Without writing a whole article about it here (Brent Ozar has several, which is where I got the idea...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2017 at 9:10 am
This will likely be the 2nd to the last update on this wonderful community effort. Thank all of you again for the great help and ideas.
I've converted the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2017 at 8:50 am
--Jeff Moden
Change is inevitable... Change for the better is not.
May 30, 2017 at 8:20 am
That's a great idea, Eirikur. Simple and will have a major impact by probably reducing the amount of work that actually needs to be done to hundreds instead of tens of...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 29, 2017 at 7:44 am
There's only one term that comes to mind after all the incredible tutelage I've received on this thread and what it has resulted in and that would be UNBELIEVABLE! --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)
May 28, 2017 at 4:24 pm
Going for the brass ring... here's a progress report.
The following code does the "temp table" optimization that Eirikur suggested. It examined 84,817 execution plans, eliminated about 6% of...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 28, 2017 at 3:10 pm
Viewing 15 posts - 14,956 through 14,970 (of 59,097 total)