Wrox Programmer Forums
Go Back   Wrox Programmer Forums > ASP.NET and ASP > ASP.NET 4 > ASP.NET 4 General Discussion
ASP.NET 4 General Discussion For ASP.NET 4 discussions not relating to a specific Wrox book
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ASP.NET 4 General Discussion 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 March 22nd, 2011, 06:05 AM
Friend of Wrox
Join Date: Aug 2004
Posts: 550
Thanks: 0
Thanked 1 Time in 1 Post
Default Performance and Maintainability issue - Urgent

Hi All

We are developing a software which will be distributed on web for different clients. Now we are facing some doubts regarding deployment.

In short, in our database we have a table where records will be updated and inserted daily by our client, say 50 records per day. So in total 1500 rows per month month for 1 client. Now if we have 100 clients, this will mean that 1,50,000 will be inserted per month, which will take the figures to million per year. This way database will become huge. More importantly we dont have huge servers or huge money to spend to get large servers. We are small start up company.

So what we are thinking is to deploy separate database and website for each client. But in terms of maintainence, it would be difficult as we will then have 100 websites and 100 databases for 100 clients.

Anyone can share their experience.

Old March 23rd, 2011, 12:41 PM
Authorized User
Join Date: Jan 2011
Posts: 86
Thanks: 1
Thanked 12 Times in 12 Posts

Hi Mike,

which database are you talking about ? Sql server (CE 4)? MySQL ? ...

In general I think you will face performance issues (or let's say you will need to seriously look at the indexes you define to prevent them) as soon as you run into millions of records and need to join this with two other medium sized tables. If you then start making snapshot tables to speed up you queries, you still end up with high maintenance.

But frankly I don't dare to give more advise as there are many more factors involved and I for instance don't understand why you would also have 100 websites..

Similar Threads
Thread Thread Starter Forum Replies Last Post
Performance issue in using XSLT Prabeen XSLT 4 July 9th, 2009 10:57 AM
performance issue keyvanjan Classic ASP Basics 0 May 23rd, 2006 10:57 AM
Transactions and performance issue avanishp General .NET 0 August 25th, 2005 09:07 AM
issue of performance alyeng2000 SQL Server 2000 6 August 20th, 2004 01:17 PM
Performance issue deyakhatib SQL Server 2000 2 June 21st, 2004 10:47 PM

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