April 3, 2014 at 5:02 am
we have in the application 4 fields
There is one field called Description and this field is non editable . Now what we want to provide a feature where user can edit and save in db. before
that description field data is coming from ETL into the Db and application uses that data to display
One more logic what i want to maintain if u r not editing app should display etl data, if edited it should display edited data
April 3, 2014 at 5:41 am
I'm not clear on how you want to edit before loading or even your approach for loading.
If you want to do some straight-up replacements with some data loaded from a text file into a staging table before loading the staging table to production, I would create a table of replacements. Then load your data from the text file into the staging table, perform your replacements and load to your production table.
If you have an application that loads and then allows a user to edit the values before they're being loaded to production, I would load into a staging table, have the application allow the user to edit the staging table and then load the data into production.
If I'm completely off base on what you're requesting, we're going to need DDL, sample data and a description of your load process. Take a look at the second link in my signature for advice on how to ask questions.
April 3, 2014 at 5:44 am
All i have understand is this, Description Field contains ETL Data.
If users want to change data , then Application is shows edited data Otherwise ETL data.
your actual question would be How to maintain the Revision History for the Edited Description Field?
April 3, 2014 at 3:46 pm
Just use 2 tables and depends on where your user view it. It can be a store procedure populating the final table for display.
You can achieve it using a view. In your SQL query, just do a case if empty ( edited DB ) then show field from ETL db.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply