tag:blogger.com,1999:blog-7325550215422085906.post6850241498025128073..comments2024-03-28T12:51:00.793+05:30Comments on DATAWAREHOUSE CONCEPTS: SCD Type 2,Slowly Changing Dimension Use,Example,Advantage,DisadvantageUnknownnoreply@blogger.comBlogger12125tag:blogger.com,1999:blog-7325550215422085906.post-40745628323803676082019-08-28T02:01:15.059+05:302019-08-28T02:01:15.059+05:30That is surrogate key only - a sequential no.! Not...That is surrogate key only - a sequential no.! Not a customer IdAnonymoushttps://www.blogger.com/profile/01457387006650116960noreply@blogger.comtag:blogger.com,1999:blog-7325550215422085906.post-77171396161940146572018-12-21T14:35:44.321+05:302018-12-21T14:35:44.321+05:30Customer key is not natural key in this scenario. ...Customer key is not natural key in this scenario. The natural key will remain same, and the primary key (customer key) is generated anew for each version.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7325550215422085906.post-67577421156572110992018-03-24T18:28:54.371+05:302018-03-24T18:28:54.371+05:30When customer key remains same, it cannot be treat...When customer key remains same, it cannot be treated as a new row and hence tracking history is impossible as the original record gets updated when key is same. Effective date or column as suggested is used in scd type 3 to maintain previous and current record only(partial history)<br />Anonymoushttps://www.blogger.com/profile/09539943481428898823noreply@blogger.comtag:blogger.com,1999:blog-7325550215422085906.post-49661269069112296022017-02-08T09:18:53.031+05:302017-02-08T09:18:53.031+05:30Customer Key should remain same. This is wrong exa...Customer Key should remain same. This is wrong example. It should have version column or effective date column or current_Record IND (Y /N)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7325550215422085906.post-34342181268299405692016-05-22T20:40:09.590+05:302016-05-22T20:40:09.590+05:30Hi Question
IN SCD2, what if source record is dele...Hi Question<br />IN SCD2, what if source record is deleted? How do we handle in SCD2 ?KS2008https://www.blogger.com/profile/04572079719744358861noreply@blogger.comtag:blogger.com,1999:blog-7325550215422085906.post-90330686243332491242016-05-22T20:39:44.466+05:302016-05-22T20:39:44.466+05:30Hi Question
IN SCD2, what if source record is dele...Hi Question<br />IN SCD2, what if source record is deleted? How do we handle in SCD2 ?KS2008https://www.blogger.com/profile/04572079719744358861noreply@blogger.comtag:blogger.com,1999:blog-7325550215422085906.post-88649292656865660612015-09-05T21:50:38.512+05:302015-09-05T21:50:38.512+05:30In scd2 we have to maintain historical data...if w...In scd2 we have to maintain historical data...if we want to change the one perticular...first look in to table by using lookup...if the record not exist then directoly insert...if It alredy exist then change it with start and end date ...start date with current sysdate and end with flag no like 9999Anonymoushttps://www.blogger.com/profile/04506391163422177359noreply@blogger.comtag:blogger.com,1999:blog-7325550215422085906.post-33955117778605722772015-04-05T13:48:08.789+05:302015-04-05T13:48:08.789+05:30differences in sap bods 4.0 and 4.1 and 4.2
differences in sap bods 4.0 and 4.1 and 4.2<br />dharanihttps://www.blogger.com/profile/05452240944893958457noreply@blogger.comtag:blogger.com,1999:blog-7325550215422085906.post-75490319614994877192014-01-17T17:39:17.489+05:302014-01-17T17:39:17.489+05:30The complexity is with it's execution, the exe...The complexity is with it's execution, the execution with max function will always be time consuming. Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7325550215422085906.post-20402557125654823762013-10-02T00:43:30.438+05:302013-10-02T00:43:30.438+05:30No increased complex ETL with Pentaho Data Integra...No increased complex ETL with Pentaho Data Integration, for it has a dedicated step for Dimension treatment. SCD 1 or 2 is click away. No need for 3.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7325550215422085906.post-55218438668237545232013-08-10T19:38:22.086+05:302013-08-10T19:38:22.086+05:30Hi,
thnx for sharing this, Can anyone explain how...Hi,<br /><br />thnx for sharing this, Can anyone explain how the customer key can be changed?<br />Sonalhttps://www.blogger.com/profile/11566344953835500449noreply@blogger.comtag:blogger.com,1999:blog-7325550215422085906.post-64743001870523606662012-10-31T18:52:35.672+05:302012-10-31T18:52:35.672+05:30In a history table, we should have a column called...In a history table, we should have a column called CURR_ROW_IND (Current Row Indicator) as a CHAR (Y/N). The current row would be Y, and all other history rows would be N. In this example, we assume that the most current address would be the one with the largest CUSTOMER_KEY for the customer. To build a query, we would have to use a GROUP BY clause and a MAX function on the CUSTOMER_KEY. Returning the results could be sluggish with a large history file. Using the clause WHERE CURR_RO_IND = Y, returns results much faster.Anonymoushttps://www.blogger.com/profile/11815523544061750473noreply@blogger.com