Post reply

Why upgrade from SQL 2000 to SQL 2005?

  • November 27, 2007 at 7:47 am

    #754561

    online indexing

    we run maintenance nightly and in sql 2000 it would bleed into working hours and we would get trouble tickets at night of people not being able to work. now, we run it nightly and no one notices

  • November 29, 2007 at 12:02 pm

    #755612

    Jack Corbett (11/27/2007)

    With respect to the features, service broker can be extremely helpful, but only if you intend to use it. Doing SOA via SQL Server (HTTP endpoints) saves you a server and an IIS install (ask your server and security guys about this one).

    Brain,

    Are you saying that directly exposing the SQL Server via HTTP endpoints is more secure or less secure than using IIS and web services written in .NET?

    Yes and no. First and foremost, if you're going to use Basic Auth, SQL Server is going to force you to HTTPS. While this is what you should be doing in IIS, you don't have to...

    As far as port, etc., that's not an issue. You can tell IIS to listen on a different port. Many of us do it all the time.

    But where it saves you is you don't have IIS and ASP.NET to contend with for vulnerabilities. Yes, vulnerabilities to the underlying http.sys will continue to affect the SQL Server implementation, but other pieces/parts of IIS and ASP.NET (such as the most recent ASP.NET vulnerability) won't affect a SQL Server based SOA. Also, you don't have a second server to contend with (most folks who can afford to keep IIS and SQL Server separate to keep fights for memory, CPU, etc. from happening between the two).

    K. Brian Kelley
    @kbriankelley

Viewing 2 posts - 16 through 16 (of 16 total)

You must be logged in to reply to this topic. Login to reply