Frequently Asked Questions

Why SQLinq?
Sometimes it can get complicated to write adhoc SQL code manually and dynamically at runtime. SQLinq was created to merge the compile time validation (using LINQ) of dynamic database queries, with an easier method of generating adhoc SQL code at runtime without requiring complex string concatenation.

If you want / need to use adhoc SQL in your application and don't want to use a heavy (and sometime difficult to use) framework like Entity Framework or LINQ to SQL, then you can use SQLinq to get the benefits of LINQ and still be able to use straight ADO.NET or some other simple data access later (like Dapper-dot-net.)

Are SQL Server and SQL Azure only supported?
Yes, only SQL Server (2005 or newer) and SQL Azure are supported since SQLinq generates T-SQL code.

If you are interested in using SQLinq with MySQL, Oracle or some other database engine, please post your questions / comments in the Discussions area. If there's a demand for it, I'd be happy to work with someone to implement it.

Why not just use Entity Framework or LINQ to SQL?
Both Entity Framework and LINQ to SQL are nice ORM tools. However, there are times when you need the higher performance of using ADO.NET directly without the overhead of ORM's such as Entity Framework or LINQ to SQL. SQLinq fits in to these scenarios nicely, allowing your code to stay simple and not have the overhead of a complex object model.
Additional Resources / Tutorials

Last edited Sep 30, 2012 at 10:08 PM by crpietschmann, version 2

Comments

Kurodo Mar 26 at 1:34 PM 
no count method...