Performance impact between NVARCHAR(MAX) and NVARCHAR(100)

Personally I am very strict to the datatypes, whether it’s for a column or parameter or just a variable. I don’t like if somebody choose them carelessly. Always the datatypes needs to used precisely. Make it as a coding standard or your own best practice but do maintain the stream. It’s always a good sign. When I reject stored procs or a design on this point, people ask me “How does it matter, if it is NVARCHAR(MAX) or NVARCHAR(100)”. My funny answer is, the figures (variable length) are not my bank balance so I don’t mind if you write 100 or 1000 or max 🙂

Anyways let’s watch the implication of NVARCHAR(MAX) and NVARCHAR(100). I am using 100 as a limit here for an example, but you can test the same with any other limit and with VARCHAR type too.

nvarchar-max-nvarchar-limit

Prasad Sahoo

Prasad Sahoo, is an enthusiast of Microsoft technologies in general and a passionate database professional, mainly focusing on SQL Server performance tuning and business intelligence. He has contributed a long time of his career working on SQL Server and other RDBMS. If he is not busy with SQL stuff then he must be watching some Hollywood movies.

Leave a Reply

%d bloggers like this: