[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 313
  • Last Modified:

ASP.net web app on a company intranet with SQK Backend

Hi

I am familiar with putting an ASP.net website on the internet with a SQL server
backend on the hosting company's servers. I now have to build a solution
for a large corporation where the SQL database will reside on their servers and
the ASP.net website viewable both on their intranet and the internet.
What is different in this type of setup? Will a usual ASP.net web app work for this?
0
Murray Brown
Asked:
Murray Brown
  • 2
1 Solution
 
MrC63Commented:
Everything should work as usual, however there are things that need to be done:

 - You need to have a fixed port number configured for the for SQL Server, and must know what this port number is. 1433 used to be the default port number depending on the specific version of MS SQL.
 
 - The firewall at the corporate SQL server location must allow traffic to pass through to the appropriate SQL server at the corporate location

You should also be aware that the performance at the hosted website will be much slower than the local Intranet site (assuming they are separate sites).  The volume of data that can sometimes be generated through various queries, etc must first be sent to the remote (hosted) site, and from there to the client via the web browser.  Both the hosted location and the corporate location will need a high quality connection to the Internet to ensure performance issues do not become a problem for clients who use the hosted site.
0
 
Murray BrownMicrosoft Cloud Azure/Excel Solution DeveloperAuthor Commented:
Thanks very much
0
 
MrC63Commented:
My pleasure, hope everything works well for you in this configuration.
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now