Post a Comment
The major change in this release has been Common Criteria support for EAL4 security controls.
What this means is that SQL Server now supports Residual Information Protection (erasing memory before the memory is allocated to a new resource), proper login statistics and auditing (like Oracle has had for years), and Column GRANT should not override table DENY.
This is one of the few products Microsoft puts out which has consistently tried to do better in terms of security and reliability. It is a completely different product than SQL Server 2000 in that regard.
When you integrate it with Active Directory and IIS 6.0, you actually have support for very fine-grained authorization, authentication, and accounting. That is, if you do it right and plan it accordingly. There's a significant amount of infrastructure that your average ASP.NET app does not touch within SQL Server 2005, .NET 2.0, and IIS 6.
Oracle has this also, but will charge you an arm and a leg for Oracle Advanced Security or Oracle Single Sign On.
You can also build this in WebLogic, but again, you will be charged an arm and a leg by BEA.
You can build this in Apache/(Linux/BSD/Solaris)/Kerberos/Java/PHP as well, and save a lot of money. However, there's a lot of corporate apps out there that run .NET.
Again, Microsoft has put out a decent database server product and updated it with new features without gouging the customers like Oracle
.







