Devart LINQ to SQL support in dotConnect for SQL Server
Posted: Wed 24 Mar 2010 11:44
Hello,
I've been using the LINQ support in dotConnect for Oracle for quite some time now.
I need to have the ability to connect my application to a number of different database types without making any changes to my code. All my DB access is performed through LINQ. I'm particular interested in switching between Oracle & MS SQL Server.
In theory, this should be an easy task as the LINQ code is not depended on the type of the database.
In practice though, i see some potential pitfalls. For starters, there is no LINQ to SQL support in dotConnect for SQLServer! And before anyone says that the Microsoft implementation will do just fine and there is no need for such a thing, i will mention that there is a number of Devart extensions that are implemented in dotConnect for Oracle and not available in Microsoft implementation. For instance, one of my favorite is the DataContext.Query method that gets an SQL string and returns an IQueryable. This method is used in my application in a large number of places. How i'm i supposed to go without it in an SQL Server installation?
I've been using the LINQ support in dotConnect for Oracle for quite some time now.
I need to have the ability to connect my application to a number of different database types without making any changes to my code. All my DB access is performed through LINQ. I'm particular interested in switching between Oracle & MS SQL Server.
In theory, this should be an easy task as the LINQ code is not depended on the type of the database.
In practice though, i see some potential pitfalls. For starters, there is no LINQ to SQL support in dotConnect for SQLServer! And before anyone says that the Microsoft implementation will do just fine and there is no need for such a thing, i will mention that there is a number of Devart extensions that are implemented in dotConnect for Oracle and not available in Microsoft implementation. For instance, one of my favorite is the DataContext.Query method that gets an SQL string and returns an IQueryable. This method is used in my application in a large number of places. How i'm i supposed to go without it in an SQL Server installation?