How the problem of "datastore configuration" will be handled in SQL server?

Question

0.00/5 (No votes)

See more:

SQL-Server-2008R2

, +

Hi All
I was wondering over a problem related to "Datastore Configurations". If there are multiple Source and Target tables each with identical structures, only different kind of data stored.
For example Transactional tables of CountryA and CountryB have same structure, only holds different variety of data since information is being fetched from different regions, so that we need not recreate various dataflows mulitple times during the ETL processes using the ETL tools.
How to implement such requirements in MS- SQL server?

What I have tried:

Tried in different database server systems(SAP R3) using and ETL tool, however got to implement the same concept using the MSSQL server currently chosen as one of the backends.

Posted 26-Jul-16 23:56pm

mousau

Updated 27-Jul-16 0:30am

v2

Add a Solution

Comments

Richard Deeming 27-Jul-16 8:00am

That sounds like a very poor database design. Better to have a single table to store the transaction details, with a foreign key to a "countries" table to identify which country it belongs to.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)