ASP.NET application perfomance

Hi,

     Our team is building a customized ERP application with c#,asp.net,mssql 2008 which almost all are postlogin pages. Below are the more details.

2 servers - 1. Application with webpages and reports , 1.DB server (only database - ms sql 2008)
Total Pages - 200 to 250 .aspx pages
Reports - 75 reports with 10 types of filtering in each report.
Approximate number of users -  250 users. But will increase more in future.
Application type - Very critical billing application.

Our perfomance testing is showing good results. But reports we are yet to test..

At present we have setup the aspx pages & reports in 1 server and database in another. Is this advisable ? . Reports are used a lot by many users parallely.  Should we continue as it is or else have reports in database server seperatly ?.. Please advise !!

Thanks !!
codeoxygenAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

codeoxygenAuthor Commented:
I remember someone told us to have seperate mirroring concept of DB and have reports on that server.. Please advise the right way ..

Thank you in advance !!
0
Bob LearnedCommented:
I will assume that you are talking about SQL Server Reporting Services (SSRS), until otherwise indicated.

Here are my initial thoughts:

What is the expected user load at its peak?  

Will the process continue to grow, and what is the expected growth rate?  

Are you eventually going to need load balancers, and multiple servers in a web farm?

I prefer to have everything together in one server, but if you expect to grow, then you could run into a performance problem later in the process.  You could always start with a single server, and then expand to multiple servers in the future.  That should be an easy transition, because you would only need to change the connection strings to point to a different server.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
ASP.NET

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.