codeoxygen
asked on
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 !!
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 !!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you in advance !!