Field Data Types in SQL SERVER

[Larry Hunter]

Hi -

I am working to upgrade an ACCESS system to SQL Server 7 and I had a question
about the use of certain data types in SQL Server tables.

In selecting the proper data type to hold textual data which is more efficient
"VarChar" or "nVarChar"? The amount of data to be held in these fields will
never exceed 1000 characters.

Many thanks for any insights

Larry

[D. Patrick Hoerter]

Larry,

use varchar for non-Unicode, and nvarchar for Unicode. The storage
requirements for a Unicode (nvarchar) are twice as large as for a
non-Unicode (varchar).

Regards,
D. Patrick Hoerter

Larry Hunter wrote in message <38ce6b9f$1@news.devx.com>...
>
>
>Hi -
>
>I am working to upgrade an ACCESS system to SQL Server 7 and I had a
question
>about the use of certain data types in SQL Server tables.
>
>In selecting the proper data type to hold textual data which is more
efficient
>"VarChar" or "nVarChar"? The amount of data to be held in these fields
will
>never exceed 1000 characters.
>
>Many thanks for any insights
>
>Larry

[C. E. Buttles]

Welcome back! Hope all is well.

"D. Patrick Hoerter" <dphwebAT@bellatlanticDOT.net> wrote in message
news:38d44c6e$1@news.devx.com...
> Larry,
>
> use varchar for non-Unicode, and nvarchar for Unicode. The storage
> requirements for a Unicode (nvarchar) are twice as large as for a
> non-Unicode (varchar).
>
> Regards,
> D. Patrick Hoerter
>
> Larry Hunter wrote in message <38ce6b9f$1@news.devx.com>...
> >
> >
> >Hi -
> >
> >I am working to upgrade an ACCESS system to SQL Server 7 and I had a
> question
> >about the use of certain data types in SQL Server tables.
> >
> >In selecting the proper data type to hold textual data which is more
> efficient
> >"VarChar" or "nVarChar"? The amount of data to be held in these fields
> will
> >never exceed 1000 characters.
> >
> >Many thanks for any insights
> >
> >Larry
>

[D. Patrick Hoerter]

C.E.,

Thanks! It's great to be back...I moved, so I was offline for a little
while during the transition. Now I'm settled in, so I should be in here
often again.

Thanks,
D. Patrick Hoerter


C. E. Buttles wrote in message <38d65355$1@news.devx.com>...
>Welcome back! Hope all is well.
>
>"D. Patrick Hoerter" <dphwebAT@bellatlanticDOT.net> wrote in message
>news:38d44c6e$1@news.devx.com...
>> Larry,
>>
>> use varchar for non-Unicode, and nvarchar for Unicode. The storage
>> requirements for a Unicode (nvarchar) are twice as large as for a
>> non-Unicode (varchar).
>>
>> Regards,
>> D. Patrick Hoerter
>>
>> Larry Hunter wrote in message <38ce6b9f$1@news.devx.com>...
>> >
>> >
>> >Hi -
>> >
>> >I am working to upgrade an ACCESS system to SQL Server 7 and I had a
>> question
>> >about the use of certain data types in SQL Server tables.
>> >
>> >In selecting the proper data type to hold textual data which is more
>> efficient
>> >"VarChar" or "nVarChar"? The amount of data to be held in these fields
>> will
>> >never exceed 1000 characters.
>> >
>> >Many thanks for any insights
>> >
>> >Larry
>>
>

[Joe Gerstl]

When would I need to use Unicode? Is it required to stored data from a double-byte
character set??

"D. Patrick Hoerter" <dphwebAT@bellatlanticDOT.net> wrote:
>C.E.,
>
> Thanks! It's great to be back...I moved, so I was offline for a little
>while during the transition. Now I'm settled in, so I should be in here
>often again.
>
>Thanks,
>D. Patrick Hoerter
>
>
>C. E. Buttles wrote in message <38d65355$1@news.devx.com>...
>>Welcome back! Hope all is well.
>>
>>"D. Patrick Hoerter" <dphwebAT@bellatlanticDOT.net> wrote in message
>>news:38d44c6e$1@news.devx.com...
>>> Larry,
>>>
>>> use varchar for non-Unicode, and nvarchar for Unicode. The storage
>>> requirements for a Unicode (nvarchar) are twice as large as for a
>>> non-Unicode (varchar).
>>>
>>> Regards,
>>> D. Patrick Hoerter
>>>
>>> Larry Hunter wrote in message <38ce6b9f$1@news.devx.com>...
>>> >
>>> >
>>> >Hi -
>>> >
>>> >I am working to upgrade an ACCESS system to SQL Server 7 and I had a
>>> question
>>> >about the use of certain data types in SQL Server tables.
>>> >
>>> >In selecting the proper data type to hold textual data which is more
>>> efficient
>>> >"VarChar" or "nVarChar"? The amount of data to be held in these fields
>>> will
>>> >never exceed 1000 characters.
>>> >
>>> >Many thanks for any insights
>>> >
>>> >Larry
>>>
>>
>