Saturday, February 12, 2011

Security in SQL Server 2005 VS SQL Server 2000


Security in SQL Server 2005 VS SQL Server 2000


SQL Server 2000

1.Security:
Owner = Schema, hard to remove old users at times
2.Encryption:No options built in, expensive third party options with proprietary skills required to implement properly.
3.High Availability:Clustering or Log Shipping require Enterprise Edition. Expensive hardware
4.Scalability:Limited to 2GB, 4CPUs in Standard Edition. Limited 64-bit support.


SQL Server 2005

1.Security:
Schema is separate. Better granularity in easily controlling security. Logins can be authenticated by certificates.
2.Encryption:Encryption and key management build in.
3.High Availability:Clustering, Database Mirroring or Log Shipping available in Standard Edition. Database Mirroring can use cheap hardware.
4.Scalability:4 CPU, no RAM limit in Standard Edition. More 64-bit options offer chances for consolidation.

1)-In SQL SERVER 2000 there where maximum 16 instances but in 2005 you can have up to 50 instances.
2)-Database mirror concept supported in SQL SERVER 2005 which was not present in SQL SERVER 2000.
3)-SQL SERVER 2005 has reporting services for reports which is a newly added feature and does not exist for SQL SERVER 2000.It was a separate installation for SQL Server 2000.
4)-SQL Server 2005 introduces a dedicated administrator connection (DAC) to access a running server even if the server is not responding or is otherwise unavailable. This enables you to execute diagnostic functions or Transact-SQL statements so you can troubleshoot problems on a server. which was not present in SQL SERVER 2000.

No comments:

Post a Comment