Great video Erik. The dreaded 'put everything into large varchar fields' antipattern rarely mentions the memory issue even though it can have pretty dire consequences as you prove. QQ for you though .... how much memory would be allocated to a varchar(max) and nvarchar(max) field? Also, which is the best field in the Actual Execution Plan to ascertain how much memory was actually needed for the data (ie. to see how much the plan actually wasted)?
The grant for max fields is still about half. It’s estimated size of data. The best place to see memory grant details in actual plans is in the memory grant property of the root node.
![Waiting due to memory grants [7 of 7] | Azure SQL for beginners](http://i.ytimg.com/vi/kzc-LX7T1lg/mqdefault.jpg)
Useful video!thank you!
Usefulness is next to cleanliness, or something.
Great video Erik. The dreaded 'put everything into large varchar fields' antipattern rarely mentions the memory issue even though it can have pretty dire consequences as you prove. QQ for you though .... how much memory would be allocated to a varchar(max) and nvarchar(max) field? Also, which is the best field in the Actual Execution Plan to ascertain how much memory was actually needed for the data (ie. to see how much the plan actually wasted)?
The grant for max fields is still about half. It’s estimated size of data. The best place to see memory grant details in actual plans is in the memory grant property of the root node.
"Thumbs are fingers, hot dogs are sandwiches"; lol; I watch for the quality content, and stay for the entertainment
Oysters are nachos.