Hello Imar,

I have gone through your 2 books (Instant results & Beginning Asp.Net 3.5 ….). No doubt both are very nice and illustrative.

You have shown many methods dealing with database and play with data controls. But I am confused about what to use when?
For example you have used stored procedures with SqlDataSource and ObjectDataSource both, then

1.) Which method is most appropriate and fast in accessing database and secure too.

2.) Also in Asp.Net 2.0 you have emphasized on Business Logic with ObjectDataSource but with the invent of Asp.Net 3.5 should we still use Business Logic? Because in Beginning Asp.Net 3.5 …. you have used only SqlDataSource and no BL but still developed well running website.

3.) Can’t we use LINQ & DataContext as substitute for BL & stored procedures?

4.) Do we actually need Stored Procedures for better site?

5.) Even if we use stored procedures than is it easy to deploy the modified sproc in database at remote server?

I am really very confused about choosing right choice. Kindly sort out the problem.

Thanks...

The answer is: it all depends ;-)

The SqlDataSource is great for simple, small sites. They are easy to develop and understand, and quick to implement. But as soon as your site starts to grow, they are no longer the best option as you'll have SQL statements sprinkled all over the place. That's where I typically start using BOs with stored procedures under the hood.

Linq to SQL (or better yet, the Entity Framework) are a very compelling alternative, one I use more and more (especially with Code First in EF) and to a large extent they minimize the need for sprocs.

I would still use sprocs for intensive database processing or query logic.

Hope this helps,

Imar

__________________
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Follow me on Twitter

Author of Beginning ASP.NET 4.5 : in C# and VB, Beginning ASP.NET Web Pages with WebMatrix
and Beginning ASP.NET 4 : in C# and VB.
Did this post help you? Click the button below this post to show your appreciation!