Sql difference between nvarchar(50) and nvarchar(MAX)

Question

1.00/5 (3 votes)

See more:

I wondering is there any benefits of reducing the value limit?
Why we don't just give the (MAX) directly in any case
is that affects on the database or somthing?

What I have tried:

i used to do that
giving the max value what ever the length i need,
just give it nvarchar(MAX)
is that wrong?

Posted 16-May-17 2:52am

XRushdy

Updated 16-May-17 7:53am

Add a Solution

Comments

[no name] 16-May-17 9:27am

What is it exactly that you would like us to tell you that a simple google search could not?

PIEBALDconsult 16-May-17 9:29am

Yes, there is.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

ZurdoDev · Answer 1 · 2017-05-16T07:53:00

NVARCHAR(MAX) is stored on the database differently so that scenario is pretty clear.

I would think your question is more like "what is the difference between NVARCHAR(50) and NVARCHAR (500)?" assuming that 500 will nearly always hold what you need. It makes it confusing to see a field named last_name that is NVARCHAR (500). True, it won't make any difference internally to SQL but why give the impression that it can hold that much data and also what if you have a bug that ends up adding lots of data? You won't catch it right away.

If you are trying to decide between NVARCHAR (25) and NVARCHAR (50), then clearly go with 50 but don't do magnitudes higher than what you need. It just confuses people.

OriginalGriff · Answer 2 · 2017-05-16T04:10:00

Solution 1

See here: varchar(max) vs varchar(255)[^]

Posted 16-May-17 4:10am

OriginalGriff