How big you do your nvarchar ()

Question

When developing a database, what decisions do you make when determining how big your nvarchar is.

If I were to create an address table, my gut response would be to address bar 1 to be nvarchar (255), like the old access database.

I found that using this confused me with the old "String will be truncated." I know that this can be prevented by limiting the input field, but if the user really has an address bar that is longer than 255, this should be allowed.

How can I make my nvarchar (????)

Answer 1

: , .

. 10-20 . . E-Mail , 50-100 . - , 50 , . , - .

varchar/nvarchar , . , SQL Server 8060 . 10 NVARCHAR (4000), .... (, , SQL Server ).

, NVARCHAR/VARCHAR (MAX) - , , "", .

NVARCHAR vs. VARCHAR: , "" , , , ASCII? - VARCHAR ( ( "?" ). - (, , ..) VARCHAR.

: NVARCHAR - SQL Server. , - ?:-) .

Answer 2

nvarchar :-) varchar.

100 1000 . - , , , SQL , .

, , . varchar (200), , , > 200. INSERT UPDATE: .

255 "limit" SQL Server 6.5, vachar 255. SQL Server 7.0 + 8000 unicode

Edit:

nvarchar: , , , . , .

: varchar vs nvarchar performance

unicode , DBA ...

Answer 3

, . , 255. - .. , , 1000.

, , - , siez, zip- NI- ..

Answer 4

, , , .., . , 50 , , , , . . , 100 ( 200, 100 - " " ). , , , max(len(FirstName)). ? - 50 ? , , , . , , , /.

; nvharchar(max). , , . , .