|
Home > Archive > IIS Server > December 2004 > Hosting ASP app
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| We're creating a hosted ASP app that companies will subscribe to. Each
company will have their own SQL Server database. Some companies will have 1
user, some as many as 25. Question is: is it better to have each company
in their own website on a multi-site server or to have a single website
where each user has their own connection string to a different database?
What are pros/cons? What's a good book to read up on issues like this?
What server configurations should be considered?
TIA!
| |
| Jeff Cochran 2004-12-29, 2:48 am |
| On Tue, 28 Dec 2004 15:14:00 -0800, "Joe" <Dexter@newco.com> wrote:
>We're creating a hosted ASP app that companies will subscribe to. Each
>company will have their own SQL Server database. Some companies will have 1
>user, some as many as 25. Question is: is it better to have each company
>in their own website on a multi-site server or to have a single website
>where each user has their own connection string to a different database?
>What are pros/cons? What's a good book to read up on issues like this?
>What server configurations should be considered?
My opinion would be that these are questions you should have answered
in the design pahse of the application, not after you've created it.
None of these are answers you'll find in a book, and none are any that
can be given a simple answer to. They depend on the application use
and design, as well as reqources available, server loading, network
design and a whole lot of other factors. That means you'll likely
need to be testing a number of configurations to see what works best
for you, with your current usage and expected growth, as well as a
plan for scaling the system as business grows.
Good luck in your planning and testing.
Jeff
| |
| Don Grover 2004-12-29, 2:48 am |
|
"Joe" <Dexter@newco.com> wrote in message
news:etixrLT7EHA.3700@tk2msftngp13.phx.gbl...
> We're creating a hosted ASP app that companies will subscribe to. Each
> company will have their own SQL Server database. Some companies will have
> 1
> user, some as many as 25. Question is: is it better to have each company
> in their own website on a multi-site server or to have a single website
> where each user has their own connection string to a different database?
> What are pros/cons? What's a good book to read up on issues like this?
> What server configurations should be considered?
>
> TIA!
>
>
Hi Joe
My suggestion is to develop a an application for testing server & client
load and setting up your requirements, the number of users is irrelevant if
they are not doing anything but browsing static pages, if complex database
queries are run then that's another matter and is dependant on the load
placed on that server.
If a lot of reports are created on the fly be a client queering a database
this can also put a significant load on server to resolve all the html
report output.
There are so may factors that can impact a web application also including
how well the code it written
As I said, I would produce a test application then hire a consultant to
evaluate your requirements and recommend what way you should go, he could
also advise how you can brand your site to use the same interface for
multiple companies ect..
Using a separate db or just setting a companyid in a db field is dependant
on if there will be any common data operation or collection across companies
ect..
Regards
Don Grover
dgrover@assoft.com.au
|
|
|
|
|