Home > .net 3.5, c#, LINQ, Oracle, Visual Studio 2008 > LINQ and Full Oracle Support

LINQ and Full Oracle Support

August 2, 2007

Unfortunately, it appears that Microsoft and Oracle still have not found a way to the light.  The latest Beta 2 is still locked to only support provisioning objects from MSSQL data sources.  Even if you have the Oracle client loaded, use OLEDB (or Oracle, tried both), and have added the database to your Data Connections list, you get an error when you try to drop a table on to the builder.

“The selected object(s) use an unsupported data provider.”

Clicking help tells us that:

This message appears when you drag items that do not use the .NET Framework Data Provider for SQL Server from Server Explorer/Database Explorer onto the Object Relational Designer (O/R Designer).

The O/R Designer supports only data connections that use the .NET Framework Provider for SQL Server. Only connections to Microsoft SQL Server or Microsoft SQL Server Database File are valid.

To correct this error:

  • Add only items from data connections that use the .NET Framework Data Provider for SQL Server to the O/R Designer.

So, for now, my class libraries will remain in tact—you can LINQ pre-created objects coming from Oracle, just not directly to Oracle tables.  I checked CodePlex and didn’t see anything yet, but I’m sure it will get there.  Enough .NET developers still code against Oracle that without support, it will be hard for organizations to buy into the transition (no one wants half–and-half coding).


  1. Sgt13Echo
    March 26, 2008 at 1:01 pm

    Has this been resolved?

  2. March 26, 2008 at 1:54 pm

    Not that I know of… the new ODP.net for 11g (the beta one) works well in VS2008, but there isn’t a connector for LINQ.

    I have read that the new ADO.NET Entity Framework DOES connect to Oracle, which you could then use LINQ to iterate over those–I just haven’t had time to wire up a demo and test it.

  3. Joe West
    April 3, 2008 at 1:48 pm

    still no solution for this?

    – J

  4. April 9, 2008 at 12:23 pm

    @Joe West-

    So far, it looks like Oracle will focus on the ADO.NET Entity Framework.


    Unfortunately, that slates for 3+ months after RTM… which, since it’s only in beta 2, who knows if that’s this year or next.

  5. July 17, 2008 at 1:46 am

    Hi David (and Joe!)

    I’d be interested to get your feedback on Mindscape LightSpeed (http://www.mindscape.co.nz/products/LightSpeed/) which includes a complete LINQ provider and support for Oracle. There is even full Visual Studio 2008 designer integration with database round tripping (update database from model, update model from database etc to keep in sync).

    Just to be clear, I do work for Mindscape so I won’t make this sound too salesy!

    If you’d be interested in having a play and maybe reviewing it, feel free to email me – the more feedback we get the better 🙂


    John-Daniel Trask

  6. July 17, 2008 at 5:27 am

    @John-Daniel Trask-

    Sounds great; I’ll download it as soon as I get into the office and give it a whirl. 🙂

  7. May 30, 2009 at 9:17 pm

    I get the error even though I am using SQL Server. Apparently you must not be using a to-ODBC connection. This is true for SQL Server, Oracle, or whatever. The easiest way to overcome this with SQL Server is to use the SQL Server Client service, but wait THAT SERVICE WON’T LOAD on my box. Errrgh!


  1. No trackbacks yet.
Comments are closed.
%d bloggers like this: