Wrox Programmer Forums
|
ASP.NET 1.0 and 1.1 Professional For advanced ASP.NET 1.x coders. Beginning-level questions will be redirected to other forums. NOT for "classic" ASP 3 or the newer ASP.NET 2.0 and 3.5
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ASP.NET 1.0 and 1.1 Professional section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old September 27th, 2006, 03:06 AM
Authorized User
 
Join Date: Mar 2006
Posts: 48
Thanks: 0
Thanked 0 Times in 0 Posts
Default performance of web application

hi all,

I would like to know about the common ways of retriving data from database. I have developed an application using asp.net(vb.net), sql server 2000. Somewhere I have used stored procedures but in most the the pages I have written insert, update and select queries in codebehind page and used sql command object to execute the queries.

I have used mixture of connected and disconnected architecture. As this is my first asp.net project I don't know whether such conding style have bad impact on performance of application.

as this is internal application and we are hosting it on our own web server the security issue may not arise.

Will writing queries in codebehide page degrade the performance of application. The database server and web server are on the same machine.

Do I have to convert all the queries into stored procedures? Is is a very bad practise write the queries in codebehind pages??

Kindly share your experiences. So that I can improve my knowledge regarding the performance of application.

 
Old September 27th, 2006, 04:19 AM
Friend of Wrox
 
Join Date: Aug 2004
Posts: 550
Thanks: 0
Thanked 1 Time in 1 Post
Default

Hi Swati

Definately using stored procedure would increase the application performance, firstly bcoz they are pre-complied, secondly queries where results are obtained after executing 2-3 queries can be done in a single stored procedure.

But if ur application is not that big, and hosted internally, then there should not be signification difference in performance.



Regards
Mike
 
Old September 28th, 2006, 05:30 AM
Authorized User
 
Join Date: Mar 2006
Posts: 48
Thanks: 0
Thanked 0 Times in 0 Posts
Default

hi,

Thanks for your reply. I was afraid whether i need to convert all the front end quesries to back end. but the application is not too heavy. I think internet connection speed affects the loading of the pages.

 
Old September 28th, 2006, 06:56 AM
Friend of Wrox
 
Join Date: Aug 2004
Posts: 550
Thanks: 0
Thanked 1 Time in 1 Post
Default

Yes Swati

You are correct, since your application is an internal application and doesn't have much load balancing, you can continue with front end queries, no need to convert your queries to Stored Procedures.

Any other doubts, do let us know.

Regards
Mike





Similar Threads
Thread Thread Starter Forum Replies Last Post
Difference between web application and web site manojm39 ASP.NET 2.0 Basics 2 August 10th, 2007 09:06 AM
performance tuning of asp.net web application swati_joshi ASP.NET 1.0 and 1.1 Basics 3 July 24th, 2006 09:42 AM
performance tuning of asp.net web application swati_joshi ASP.NET 1.0 and 1.1 Professional 1 July 14th, 2006 08:46 PM
Consuming web service with dismal performance jcrossett ASP.NET 2.0 Professional 0 December 13th, 2005 11:19 AM
Developing a web site not a web application mkerchenski ASP.NET 1.0 and 1.1 Basics 8 May 25th, 2004 09:03 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.