Andrew J. Kelly is a Sr. Technology Subject Matter Specialist with B3 Group Inc. who lives in Clarkdale, AZ.. He has over 20 years’ experience with relational databases and application development but his main focus now is SQL Server. In addition to general SQL Server training and Mentoring he specializes in Performance, Scalability and Maintainability of large scale SQL Servers. He is a regular speaker each year at many conferences and user groups. He is a contributing editor and writer for SQL Server Pro and has been a Microsoft Data Platform MVP for 18 years.

Andrew J. Kelly has submitted 6 sessions for SQLBits 2020, although the agenda hasn't been chosen yet. See all submitted sessions.

Pending Sessions

This session covers the fundamentals of exactly what a Clustered Columnstore Index is, how it works and why you should use it. A must attend session for anyone planning on using CCI.
If you are planning to implement CCI in your production environment you need to be aware of certain aspects before you start. This session outlines key areas that you need to include in your planning beforehand.
This session covers the fundamentals of exactly what a Clustered Columnstore Index is, how it works and why you should use it. A must attend session for anyone planning on using CCI.
If you are planning to implement CCI in your production environment you need to be aware of certain aspects before you start. This session outlines key areas that you need to include in your planning beforehand.
This session covers the fundamentals of exactly what a Clustered Columnstore Index is, how it works and why you should use it. A must attend session for anyone planning on using CCI.
If you are planning to implement CCI in your production environment you need to be aware of certain aspects before you start. This session outlines key areas that you need to include in your planning beforehand.

Sessions

Previous Sessions

The Query Store functionality in SQL Server 2016 will change the way we look at performance going forward. Come see why.
Start your database off right so you can scale when you need to