SQL Server Performance

SQL Server Internet Access

Discussion in 'General DBA Questions' started by KirbyWallace, Jan 26, 2006.

  1. KirbyWallace New Member

    For a SQL Server serving as a database to a web application, I can see no reason why the SQL Server itself should have ANY WAN connectivity at all. The web app has two-way comm with the internet (obviously) but the sql server should be serving no one but the application. The app serves the internet.

    So I have disabled all access to the WAN for SQL Server, and, as expected, the web app continues to run just fine (it's a local trip to the sql server for it).

    What valid, or more importantly, what good reasons are there for giving SQL Server access to the WAN?

    'preciate it!

  2. ghemant Moderator

    Hi,<br />assumed that you are giving access to your SQL BOX through the WEB API and thus its not necessary to give access to wan , but now in this case as your Web Server / Web App has two way communication you need to tighten security of it.<br /><br /><img src='/community/emoticons/emotion-1.gif' alt=':)' /><br />Regards<br /><br />Hemantgiri S. Goswami<br />ghemant@gmail.com<br />"Humans don't have Caliber to PASS TIME , Time it self Pass or Fail Humans" - by Hemantgiri S. Goswami<br />
  3. Twan New Member

    Hi ya,

    In over 15 years of SQL I have never been able to find a valid reason for exposing a SQL box directly to the web... however there may be reasons for exposing it to a WAN if you had multiple geographically separate web farms, talking back to a single master database server


Share This Page