Fast Guide: Controlling access to SQL Server
One of your top priorities as a DBA (maybe the top priority) is to secure your SQL
Servers, the home to your customer details, human resources data and all business-critical
information. You must not only protect SQL Server against external
threats, but the
much-more-common internal threats -- and the measures you take to control access will go a long way
in achieving that. This guide will walk you through key tips and expert advice to help you control
internal and external access to SQL Server, and it will highlight access control enhancements in
SQL Server 2005.
TABLE OF CONTENTS
Controlling internal access
Controlling external access
SQL Server 2005 access control
Additional security resources
If you're running SQL Server in an environment where you don't want computers to access it, you
must hide the instance from network discovery.
view of SQL Server
Hackers can devastate your SQL Server workflow and cripple your company's business. Learn the four
primary methods used to hack into SQL Server.
SQLPing to prevent outside access
Make sure no listening ports are open for public access on your SQL Server machines -- or you could
be relaying sensitive database information to the outside world.
permissions in SQL Server 2005
New security features in SQL Server 2005 make it easier to manage and grant permissions on a more
granular basis. Get an overview of new features and functions.
This was first published in November 2005