If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Data Access, Manipulation & Batch Languages > ASP > 3 servers?

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 02-27-06, 09:30
poison_chicken poison_chicken is offline
Registered User
 
Join Date: Feb 2006
Posts: 34
3 servers?

does asp run on the web-server?

in other words, i am trying to build a web-based database application. i will need 1. web server, 2. sql server, 3. asp application server?

or does the asp application run from web server?
Reply With Quote
  #2 (permalink)  
Old 02-28-06, 16:09
gflken gflken is offline
Registered User
 
Join Date: Feb 2006
Location: Seattle / Eastside
Posts: 10
The web server will run asp web applicatoins - you don't need a separate server for this.

Could you clarify if you are planning to build an application (com written in vb, etc) accessed by asp (page.asp), or are you planning on using asp.net framework to access MS SQL?

Depending on the level of involvment, you may will likely need your own server or a host that will allow custom apps / dlls
Reply With Quote
  #3 (permalink)  
Old 03-01-06, 01:44
poison_chicken poison_chicken is offline
Registered User
 
Join Date: Feb 2006
Posts: 34
i am "planning" to use asp.net framework to access MS SQL.
Reply With Quote
  #4 (permalink)  
Old 03-01-06, 02:27
kropes2001 kropes2001 is offline
Registered User
 
Join Date: Nov 2005
Location: Honolulu HI
Posts: 118
you only need items 1 and 2.

personally though... i would suggest that you simply start off with setting up a hosting account someplace and then growing into having your own servers...

from a person that has been down that road. i can tell you that the goal of your new business is
1) to get up and running and make money.
2) conserve your resources (time and money)
3) market your services
4) expand as needed

if you start out with trying to have you own servers, you will spend a lot of time trying to manage the servers instead of working on your application. when you are focused on your application, your server maintenance may start falling behind in patches and security.

while you are still growing, let someone else have those headaches. you focus on building the application and the business. especially since you are asking that question to begin with... that tells us that you may have a steep learning curve ahead of you to tackle everything at once.

plus. just setting up a hosting account someplace is more cost effective right now. they take care of all backups and such and you can get a hosting account with everything you need (like with me) for $25-$36 a month. i have see other companies offering it even cheaper than that... like $9 a month (although i am not sure how they are doing it and havnig any decent services.)

if you go full load with getting servers and rack space and such, you are immediatly into $200 a month minimum for a quality service. plus YOU are responsible for backups and everything else in between.

once you start needing to expand and expand to the point where you need your own hardware... migration is relatively painless...
__________________
.
.
http://www.GetMySiteOnline.com - Can you help me Get My Site Online ? (Yes. That is EXACTLY what we do.)

http://www.GetMySiteOnline.com/FightingSpam/
__________________________
caeli enarrant gloriam Dei !
Reply With Quote
  #5 (permalink)  
Old 03-01-06, 09:12
poison_chicken poison_chicken is offline
Registered User
 
Join Date: Feb 2006
Posts: 34
thanks kropes...thats good advice
Reply With Quote
  #6 (permalink)  
Old 03-01-06, 12:19
John Grubb John Grubb is offline
Registered User
 
Join Date: Jan 2006
Posts: 27
In this case, you don't "need" more than 1 server to get started. Asp can execute in the web server, or you can use a thin layer on the WS and call an app sever remotely. Application design is key here. You can run the asp and connect to a database directly.

In most cases, you want to at least conceptually break the app into Presentation (ie, the WS), Logic (the "application server") and Data (the DB). This gives you some flexibilty in where you host the actual fuctionality, as well allowing some more options for scaling.

Example. You can build an asp.net layer that makes soap calls for the data to build the presentation layer. The Soap endpoint can local or remote. The Endpoint can be anywhere, and abstract the puts and gets to other soap calls, or direct DB access. All 3 layers can be hosted locally, or disconnected. This isn't the only option, either.

Jay Grubb
Technical Consultant
OpenLink Software
Web: http://www.openlinksw.com:
Product Weblogs:
Virtuoso: http://www.openlinksw.com/weblogs/virtuoso
UDA: http://www.openlinksw.com/weblogs/uda
Universal Data Access & Virtual Database Technology Providers
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On