SQL nvarchar considerations?

One row or field per address line, perhaps 100 long In ye olden days, people had to write on an envelope. No need for War and Peace epic addresses And how would you break out post code, country, town etc if it was one field. Or lookups as Astander mentioned too Anyway, don't use max: there are some overhead because it's a BLOB datatype.

One row or field per address line, perhaps 100 long. In ye olden days, people had to write on an envelope. No need for War and Peace epic addresses And how would you break out post code, country, town etc if it was one field.

Or lookups as Astander mentioned too. Anyway, don't use max: there are some overhead because it's a BLOB datatype.

1 Also a good point might be that state/country/postcode should be part of the look ups from other tables. – astander Feb 13 '10 at 12:45 1 if you only have to deal with english, then consider varchar over nvarchar as its more efficient! – Nick Kavadias Feb 13 '10 at 15:56 @Nick Kavadias: yes, I'm a believer... stackoverflow.Com/questions/35366/… – gbn Feb 13 '10 at 19:41 your not just a good lookin' dude with a handsome mullet, you're also smart!

– Nick Kavadias Feb 13 '10 at 6:54.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.