Web Application with different Databases

Question

0.00/5 (No votes)

See more:

, +

Hi All,

I want to create one web application in such a way that if tomorrow my new customer have different database . So,with minimal configuration I should connect to it.
E.g.

I created one web application and client using SQL then if another customer approaches with different database like oracle. So, I should provide a layer in such a way that application should work with Oracle and SQL (Not simultaneously ..independently)

I am looking forward with Entity Framework Code First Model where model will create DB in runtime. So, if you guys have any other better way then let me know .
Thanks

Posted 29-Sep-15 21:31pm

RAHUL(10217975)

Add a Solution

3 solutions

Add a Solution

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)

F-ES Sitecore · Answer 1 · 2015-09-29T22:36:00

You can use a database-agnostic technology like ADO.net and ODBC, and that way you just change the odbc driver in your connection string and as long as the new database has an adbc driver it *should* just work. There might still be some minor differences in odbc implementation though so you might need to tweak from of the SQL.

Given that is going to adversely impact the performance of your code for a situation that is never going to happen (Microsoft moved away from this type of solution-for-a-problem-noone-has quite some years ago), the next best way would be to abstract your data access code using a data access layer, or a repository patter type solution. When a new data store comes along you'll need to rewrite the data layer for it, but if you've done it correctly that's all you'll need to re-write and you'll be able to use any of your data access layers depending what the client uses. Google repository pattern or data abstraction patterns for more details.

amit raje · Answer 2 · 2015-09-30T03:59:00

Solution 3

Entityframework code first approach is the best known way to create such application. You just need to change connection string and done. No need to create tables again.

Posted 30-Sep-15 3:59am

amit raje

Member 10369847 · Answer 3 · 2015-09-29T22:20:00

Solution 1

Generate script for all table with master data and keep separate. this script you can place in sp into master database with parameter of database name. when you need to create new database then you can run it with your database name parameter.

Posted 29-Sep-15 22:20pm

Member 10369847