In SQL Server if you have ever analysed the plans (execution plans) using SSMS plan analysis(I am sure you have :) ), then one thing you might have noticed is thickness of arrow between the two operators.
Thickness of arrow has been used by many DBA's as an estimation of size of data.
To correct the myth/confusion, this thickness of arrow just represents the row count and not actually the size of the data.
This means you can see a thin arrow representing 4 rows, but behind that it could be xml data of GB size
so do not just rely on thickness of arrow before picking expensive operator and expensive flow of data between two operators.
enjoy
Thickness of arrow has been used by many DBA's as an estimation of size of data.
To correct the myth/confusion, this thickness of arrow just represents the row count and not actually the size of the data.
This means you can see a thin arrow representing 4 rows, but behind that it could be xml data of GB size
so do not just rely on thickness of arrow before picking expensive operator and expensive flow of data between two operators.
enjoy
No comments:
Post a Comment