Partitioning is one of those features that is available in SQL server but never really thought about until the size of the table becomes unmanagable. In this video I demonstrate how to implement partitioning on large table and the impact querying such a table has on performance. We explore how the tables performance differs for the query if it is partitioned versus if it wasn't. The intention here is to explain to the user how distributed IO can actually significantly improve performance and improve scalability when coupled with indexes. There is a common misconception that partitioning doesn't improve performance that it just helps manage the data better. However in subsequent versions of SQL server we see how Microsoft relies heavily on splitting the data and leveraging partition elimination to improve performance. A minor variation of this could be seen in segment elimination of column store indexes. Having said that partitioning on its own is not sufficient for most use cases. Then tension of the video is to clarify when partitioning should be leveraged and how it needs to be implemented in order for it to improve performance.
Partitioning also allows the user to leverage piece meal restores and read only file group which are not really covered in this video but should give the user enough of a justification to consider partitioning large tables.
Need more information?
Visit [ Ссылка ]
To know more about Jayanth Kurup visit [ Ссылка ]
Jayanth is a Microsoft SQL Server trainer / consultant with over 15 years experience. He has worked with companies like Microsoft, IBM, HCL , Wipro , WellFargo , Zeomega and many more. He is based out of Bangalore and a very active member of the SQL Server Community.
In this channel he covers complex topics related MS SQL Server , PowerBI , Azure , AWS , Powershell, SSIS , SSAS , SSRS , Machine Learning , AI , etc
You can also reach Jayanth via his LinkedIn profile below
[ Ссылка ]
