CODEWITHSUNDEEP
c#databaseoracle-database
Cliff
Cliff

Reputation: 707

connecting to a large Oracle database in C#

I'm new to Oracle in general (moving from SQL Server, not by choice), so apologies if this is a stupid question.

I've added the System.Data.OracleClient reference to my C# Windows Forms project in VS2012 , and I'm able to connect successfully to a remote Oracle database in the Data Source Configuration Wizard by selecting Dataset > Database (though not in Entity Data Model, but that's not the issue). However, when I get to "Choose Your Database Objects", I'm trying to select a significant number of them, and the application freezes when I click Finish.

The database is somewhat complex, and I will likely need most (if not all) of the tables in the coming week or so. Is there a better way to connect to the database directly, instead of going through the DSCW?

Upvotes: 0

Views: 281

Answers (3)

Bura Chuhadar
Bura Chuhadar

Reputation: 3751

You shouldn't add all the tables at once. Add the tables you want to use. Plus, you can use code first approach. (If you prefer database first still it is OK.)

Other option is that if you are using Entity Framework >= 5.0, then you can also use multiple diagrams to avoid rendering and slowness problems.

Upvotes: 0

Md. Tazbir Ur Rahman Bhuiyan
Md. Tazbir Ur Rahman Bhuiyan

Reputation: 2032

click on this link and follow the instruction. let me know if you see any success

oracle guideline: Using Oracle Developer Tools for Visual Studio

Upvotes: 0

Hambone
Hambone

Reputation: 16397

System.Data.OracleClient has been depricated for a while, last used with 2.0 I think. Oracle's ODP.net is the recommended client. It leverages OCI and can access a lot of Oracle-specific features such as bulk inserts and updates. System.Data.OracleClient was also really bad at parameters -- it had a significant performance drag if you tried to use bind variables.

If you want to use Entity, you should consider DevArt's dotConnect. The free version doesn't support Entity, but the paid one does. The paid version also does not require an Oracle client on the host machine, which last time I checked, ODP.net still does. If your employer is paying, it might be worth the upgrade to be able to use Entity.

Other than the fact that System.Data.OracleClient was not great, I can't imagine why adding a lot of DB objects would cause the freeze. Give ODP.net and/or DevArt a try.

Upvotes: 1

Related Questions