SQLBits 2014
Achieving PCI with SQL Server - Don't be the next Sony
This session covers all aspects of what you need to do, to enable the storage of card details in SQL Server and achieve PCI certification.
We will deep dive into the solutions for storing the data securely using SQL Servers encryption functionality
So you want to store credit card details in SQL Server what do you need to do?
The holding of card details means that you need to achieve PCI certification what does this mean from SQL Server perspective.
This session covers the following for SQL Server
- Protect the data
We will do an overview of all the areas and drill down into the storage of data and how that can be achieved seamlessly from the application. At the end of the session you will know what you need to do, and how to do it, to store card details in SQL Server and achieve PCI certification.
Speakers
Simon Sabin's previous sessions
Maximising everyone's super powers - Panel discussion
In this panel we will discuss approaches with leaders in the field who have first hand experience of managing neurodiversity in the work place. Welcome questions from the audience as to how everyone can maximise their and their teams super powers
Achieving PCI with SQL Server - Don't be the next Sony
This session covers all aspects of what you need to do, to enable the storage of card details in SQL Server and achieve PCI certification.
We will deep dive into the solutions for storing the data securely using SQL Servers encryption functionality
Performance tuning from the field
In this session we will look at some common practices I have seen in the field that cause performance problems. We will diagnose the cause of the problem and the resolution to the problem.
10 things you should never do with SQL Server
In this session we will look at some of the practices that you shouldn't follow when developing a SQL Server database. We will cover items such as query design, table design, indexes, constraints and more.
After this session you will have some practices that you know you should avoid in your SQL Server database if you want the best performance. If you have them you will know what you need to do to resolve them.