One method that stores the data in two different databases

Question

0.00/5 (No votes)

See more:

Hi Everyone,

I'm working on a project where I deal with multiple databases using entity framework. All databases have similar schema.

I've a scenario where I need to store data in one of the database based on one of the property of that object.

Say I've SoldIn integer property that has some integer values of States (Id of State), the product will be sold in so and so State.
What I've done is, I've written multiple methods with multiple contexts for storing the Object values in respective databases.

Now the functionality and business validations are same for all the states, Only the destination database is different.

Can anyone help me in writing the logic of this scenario in C#?

Thanks in advance.

What I have tried:

What I've done is, I've written multiple methods with multiple contexts for storing the Object values in respective databases.

Posted 15-Feb-18 6:35am

Rockstar_

Add a Solution

Comments

Richard Deeming 15-Feb-18 15:00pm

This seems like a dodgy database design. Rather than storing data from different states in different databases, they should be stored in the same database, using a foreign key relationship to the state. If necessary, you can use SQL Server's partition functions to separate the data for different states if the performance is a problem.

But failing that, you probably need to use a DTO; create the DbContext with the correct connection string based on the property; and then map the DTO to the DB entity on that context.

That then raises the issue of what happens if an entity's "sold-in" state is changed.

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)