Earlier I wrote a blog post on Forwarded Records and Performance and lots of people liked the blog post. Here is you can read the blog post SQL SERVER – What is Forwarded Records and How to Fix Them?
Here is the video which I have built on that topic.
Forwarded Records are the data row in a heap that has moved from the original page to the new page. A heap table is a table without a clustered index. When a user updates a column with a larger size of data, it is possible that a particular field now can’t fit on the same data page leaving a forwarded record of that data.
When SQL Server scans the heap to read the necessary data, they often encounter forwarding record pointers which usually exist on the different page leading SQL Server to read more pages than required while dealing with the heap. This is the reason, often performance of the heap has been very bad.
Here are my few recent videos and I would like to know what is your feedback about them. You can subscribe to my youtube channel here.
- Hide Code in SSMS – SQL in Sixty Seconds #154
- Zoom in SSMS – SQL in Sixty Seconds #153
- Transfer Schema of Table – SQL in Sixty Seconds #152
- Find a Table in Execution Plan – SQL in Sixty Seconds #151
- Transactions and Variables – SQL in Sixty Seconds #150
- Count Table in Cache – SQL in Sixty Seconds #149
- List All Sessions – SQL in Sixty Seconds #148
- Line Numbers for SSMS Efficiency – SQL in Sixty Seconds #147
- Slow Running Query – SQL in Sixty Seconds #146
- Change Database and Table Collation – SQL in Sixty Seconds #145
- Infinite Loop – SQL in Sixty Seconds #144
- Efficiency Trick – Query Shortcut – SQL in Sixty Seconds #143
- SQL SERVER – 16 CPU vs 1 CPU: Performance Comparison – SQL in Sixty Seconds #142
- SQL SERVER – TOP and DISTINCT – Epic Confusion – SQL in Sixty Seconds #141
Reference: Pinal Dave (https://blog.sqlauthority.com)