Securing a Multi-Database Application


It is difficult enough to implement database security when dealing with only a single database. If multiple databases are involved, the task of providing a security model that follows industry best practices seems insurmountable.
In this session, we will do a quick review of access security best practices and then dive into the four different methods a DBA can use to tighten cross database access security. For each one we will walk through a demo and talk about how to implement it in your own environment. We will close the session with a discussion about the advantages and disadvantages of the four methods.

Sebastian Meine

Sebastian is the SQL Stylist at sqlity.net llc (http://sqlity.net). After receiving his PhD in Computer Science at the University of Linz, Austria he spent several years at a global Fortune 50 company as software architect responsible for code quality and performance of dozens of large-scale database installations throughout the US.

In 2010, to fully engage in his passion for SQL Server, he founded sqlity.net. Since that time, he has been helping his clients to boost their SQL Server health and performance, enhance their T-SQL coding skills and tighten their SQL Server security.

A sought-after educator and published author, Sebastian shares his knowledge regularly within the worldwide SQL community through his writings and public speaking engagements. Additionally he is coauthor of tSQLt, the Database Unit Testing Framework for SQL Server. tSQLt is open source and available at http://tSQLt.org.

Sebastian is currently serving as president of the Philadelphia SQL Server User Group (http://pssug.org/), a nonprofit that is dedicated to further the education of the local SQL Server community.