Anyone see a problem with this?

Question

Anyone see a problem with this?

Viewing 2 posts - 16 through 16 (of 16 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1004414 More actions · Answer 1

Sergiy - Monday, October 22, 2018 5:08 AM
Jeff Moden - Monday, October 22, 2018 4:44 AM
I agree with you. It's been the norm rather than the exception since I can remember.
Did you see those statements - "In the last decade amount of data we collected increased by 10 .. 20 .. 50 .. whatever number of times".
That's so cool and progressive! Right?
Now, parse all those XML's, JSON's and all other data formats into a properly normalized relational data storage - where will that progress disappear?
Yep, nothing to show pretty much.
Lousy solutions are good for everyone.
Except may be for end users, but who asks them?

You definitely are preaching to the choir. It's just a small choir. 😀

--Jeff Moden

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.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Eric M Russell SSC Guru Points: 125562 More actions · Answer 2

It appears that what we're dealing with here is a "Type 2 slowly changing dimension" table. If so, then the purpose is to retain history. There should be something like an effective start date column and effective end date. Also, it helps to have an indicator column that gets updated to reflect which row is current for each (policy, customer, etc.), that way the SQL developer doesn't need to resort to using windowing or ranking functions. What I find surprising here is that neither the DBA or developer seem to agree on what this table is or how it works.

"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho