You can do this if need be. I'm doing it for one of my clients because of
the exact same cost reason for them. As to how much of a performance hit
you'll take, it will depend upon where the database server resides in
relation to the web server. There is always a penalty in performance due to
latency. This could cause your app to appear slower since you could be
running even half a second slower for database activities. To improve this
performance try limiting the number of data accesses on a page. If your
would normally return a number of datareaders, try getting one datareader
with multiple resultsets that you can iterate through. This can improve
performance because you're only using the one connection instead of
numerous. You can run a trace (using tracert at the command prompt) to find
the path to the various hosts to get an idea of where the datacenters are
actually located and this could help you figure out a rough idea of the
latency.
--
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage
"Michel Couche" <Contact //@// michelcouhe.netwrote in message
news:eV***************@TK2MSFTNGP05.phx.gbl...
Hello,
I am working on a project for a potential customer.
The project will basically involve an ASP.Net 2.0 application and a
database (ideally MS SQL). The customer has already a hosting plan but it
does not currently include a MS SQL database. This option is offered as a
rather expensive add-on (600 US $ /year).
If we need cost saving, I could offer to set-up a MS SQL 2005 DB on my own
hosting plan in a different company (I may have 10 DB's) and use it as the
database for my customer's web site.
This would be a cheaper alternative but . do you think that there would be
a efficiency penalty ? I believe that as the IIS server and the MS SQL
server resides on separate machine with their own IP's it should be
transparent for my application and there should be no penalty in terms of
user's perceived efficacy
Thanks in advance for your feedback and advice,
Michel
NB: Last indication my hosting company is physically in the US and the
customer's hosting is in the UK