Lars

BTW: Microsoft SQL Server gives a lot of possibilities: Views, Stored Procedures, Functions. Much more then other (like Postgre or MySQL). So it has no sense to put SQL code inside of C# or VB code at all. Only reason is fast development, but this is bad reason.

Sergey

---

 

Let me jump in here to provide some advice for Aristotelis: there are best practices for safety and performance reasons, you never know in you business logic, where input parameters may come from, even if not atm, in a future extension it might be passed from UI without proper check and you will be vulnerable to SQL injection. The proper alternatives are either put the SQL code into stored procedures or use Linq2SQL, where security is provided on compile and run time.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN