Migrating from Oracle to MS sql server

Question

0.00/5 (No votes)

See more:

Hi,

My application should needs to function with minimum of changes if the database platform ever changes from Oracle to SQL Server.

which DataReader objects should I use to minimize the impact of a change to the database platform in the future?

A) IDataReader
B) OleDbDataReader

Thanks in advance.

Posted 25-May-10 23:02pm

abhishekrvce

Add a Solution

2 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)

Bernhard Hiller · Answer 1 · 2010-05-26T23:50:00

Write a function which finds out which database your customer is using, then instantiate the specific type for it (i.e. OracleDataReader and SqlDataReader, resp.). They do inherit from IDataReader, hence in all the further code you need not differentiate.
Although it is true that you can connect to both SQL Server and Oracle via OleDb, I do recommend not to do so. OleDb is too unspecific when it comes to dealing correctly with some odd data types like datetime - especially localized - or guid etc.
Some functions need to be totally changed, e.g. bit operations, or getting the last insert id.

Johnny J. · Answer 2 · 2010-05-25T23:16:00

In my experience it's always best to use the data objects provided by the framework for the specific database type, e.g. SQL Server objects for SQL server access.

I don't know if any such objects are supplied for Oracle, though.

But (this might be selfevident, but just in case you don't know it) you should restrict all your database access to your data layer and keep the code separate from the rest of the code. That way, when (if) it comes to changing the DB type, you (more or less) only need to change the "using" statement... (and perhaps make minor tweaks).

If your db code is spread all over the place, then this will become a major task...

Migrating from Oracle to MS sql server

2 solutions

Solution 2

Solution 1

Add your solution here

Preview 0