Base solution for your next web application
Open Closed

Change Connection String on ASP.NET Hosting #118


User avatar
0
bigboss created

Actually, I have built my site on my localhost. I develop my site using asp.net and I have a SQL SQL 2012 db hosted on a server here. I need to build a website (hosted remotely) that will both read and write data from this database as well as a couple of other SQL SQL 2012 (maybe 2014 also) databases located on machines here.

What is the best way to accomplish this via a hosted setup it on hosting provider? I plan to host my site with <a class="postlink" href="http://www.hostforlife.eu">http://www.hostforlife.eu</a>.

What features do I need to make sure I have when trying to select a web hosting provider?

What is the best method for accessing the databases here from the remotely-hosted website? I want to make sure I'm using the best methods for speed, security, stability, etc.

Will I just access the SQL Servers here directly, or do I need to have a SQL Server running at the web host also some type of a subscription setup? I asked these question in another group and I was told to use replication to keep a copy of the databases local to the web host for performance reasons.

Any recommandations for quality ASP.NET web hosting providers in Europe? Any that you've had good service and results with?

I have no idea what the best way to accomplish this is and I'm feeling lost.

Thanks in advance for any and all information, I really appreciate it.


2 Answer(s)
  • User Avatar
    0
    hikalkan created
    Support Team

    Hi,

    Actually, this problem is completely independed from ASP.NET Boilerplate framework. To get the best answer, you should ask it in an SQL Server forum, at least on stackoverflow.

    Based on my experiences,

    1. It's best to directly connect to remote SQL server. This is the best since it's the simplest. Your application will work as same as local. If you don't expect so much concurrent users or long and heavy transactions and newtork bandwidth is enough, I would choice this.

    2. Replication is harder to setup and maintain, also you will take care of conflicts (if different applications will use different replicated servers) and other problems. But surely it's better performance to read & write local.

    3. You can implement remote façade. So, you can write a Web API layer that runs on the remote server (which is local to DB). Your application calls these web API to perform all operations.

    So, it's architectural decision, but not related or unique to ABP system.

  • User Avatar
    0
    bigboss created

    Hi Hikalkan,

    Thank you for your reply. I will post my questions on other forums. :)