Showing posts with label unicode. Show all posts
Showing posts with label unicode. Show all posts

Friday, March 23, 2012

Export Access table into MS SQL server preserving Unicode characters?

Hi,

usually, I'm not using MS servers, but I have a big problem with a
Access table.

I should create a web application for a Historical Dipartment.
They have create a populated a Access database using unicode
compression field (for ancient language).

I would like to export this table into MySQL o Postgres, but it's
impossible because when I export this table in a .txt o cvs format the
unicode charaters have been "destroyed" for memory allocation problems
(cause Access use a compression tool for unicode fields).
Also with professional tools for dump Access to another DBMS.

I would to know if using a MS SQL server I can skip this problem cause
both MSQLserver both Access are Microsoft product.

Thank you ;)
Jdreamers_spa@.yahoo.it (JJ) wrote in message news:<1b641cf1.0402030348.1ca6bdd8@.posting.google.com>...
> Hi,
> usually, I'm not using MS servers, but I have a big problem with a
> Access table.
> I should create a web application for a Historical Dipartment.
> They have create a populated a Access database using unicode
> compression field (for ancient language).
> I would like to export this table into MySQL o Postgres, but it's
> impossible because when I export this table in a .txt o cvs format the
> unicode charaters have been "destroyed" for memory allocation problems
> (cause Access use a compression tool for unicode fields).
> Also with professional tools for dump Access to another DBMS.
> I would to know if using a MS SQL server I can skip this problem cause
> both MSQLserver both Access are Microsoft product.
> Thank you ;)
> J

You could use DTS or a linked server to get the data directly into SQL
Server, provided that you define the destination columns as a Unicode
data type (e.g. nvarchar). But you might want to post this in an
Access newsgroup, as exporting data to a file with Unicode characters
intact is presumably something that has been done before (and changing
database platform to resolve an import/export issue seems a little
drastic).

Simon

Wednesday, March 21, 2012

export a table

I tried to write a package for transferring SQL 2005 table to a flat file in
Visual Studio. However I got the unicode error message at the destination
even though I only use English. Does anyone has idea? Thanks.
The message is as following :
Error: Column "Status" cannot convert between unicode and non-unicode
string data types.
Error: ... ( The same message with all the column in the source table)
Please help. Thanks.
" 00ScarlettJohnson" <EE@.yahoo.com> wrote in message
news:ekXwbLCcHHA.2552@.TK2MSFTNGP06.phx.gbl...
>I tried to write a package for transferring SQL 2005 table to a flat file
>in
> Visual Studio. However I got the unicode error message at the destination
> even though I only use English. Does anyone has idea? Thanks.
>
Sounds like source database may be using nvarchar for its columns?
Probably need to cast them (and possibly lose unicode data, but sounds like
you have none) before you export them.

> The message is as following :
> Error: Column "Status" cannot convert between unicode and non-unicode
> string data types.
> Error: ... ( The same message with all the column in the source table)
> Please help. Thanks.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||I solved the problem by adding data conversion task between source and
destination. But this does only for append. How can I do it for overwrite?
Thanks.
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:OVMWf4OcHHA.4260@.TK2MSFTNGP02.phx.gbl...
>" 00ScarlettJohnson" <EE@.yahoo.com> wrote in message
>news:ekXwbLCcHHA.2552@.TK2MSFTNGP06.phx.gbl...
> Sounds like source database may be using nvarchar for its columns?
> Probably need to cast them (and possibly lose unicode data, but sounds
> like you have none) before you export them.
>
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com
> http://www.greenms.com/sqlserver.html
>
|||Can anyone please help? Is this the correct group I post this kind of
question? Thanks.
" 00ScarlettJohnson" <EE@.yahoo.com> wrote in message
news:OgwAMpQcHHA.588@.TK2MSFTNGP06.phx.gbl...
>I solved the problem by adding data conversion task between source and
>destination. But this does only for append. How can I do it for overwrite?
>Thanks.
>
> "Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in
> message news:OVMWf4OcHHA.4260@.TK2MSFTNGP02.phx.gbl...
>
|||Hello 00ScarlettJohnson,

> Can anyone please help? Is this the correct group I post this kind of
> question? Thanks.
I'll try; No, please use "microsoft.public.sqlserver.integrationsvcs" and
I'm wondering if you mean by "overwrite" that you want it to have the data-converted
columns have the same names, yes you can do that but note you will still
be generating a new lineage for the converted column and all of the overhead
associated with that.
Thanks!
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/

export a table

I tried to write a package for transferring SQL 2005 table to a flat file in
Visual Studio. However I got the unicode error message at the destination
even though I only use English. Does anyone has idea? Thanks.
The message is as following :
Error: Column "Status" cannot convert between unicode and non-unicode
string data types.
Error: ... ( The same message with all the column in the source table)
Please help. Thanks." 00ScarlettJohnson" <EE@.yahoo.com> wrote in message
news:ekXwbLCcHHA.2552@.TK2MSFTNGP06.phx.gbl...
>I tried to write a package for transferring SQL 2005 table to a flat file
>in
> Visual Studio. However I got the unicode error message at the destination
> even though I only use English. Does anyone has idea? Thanks.
>
Sounds like source database may be using nvarchar for its columns?
Probably need to cast them (and possibly lose unicode data, but sounds like
you have none) before you export them.

> The message is as following :
> Error: Column "Status" cannot convert between unicode and non-unicode
> string data types.
> Error: ... ( The same message with all the column in the source table)
> Please help. Thanks.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||I solved the problem by adding data conversion task between source and
destination. But this does only for append. How can I do it for overwrite?
Thanks.
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:OVMWf4OcHHA.4260@.TK2MSFTNGP02.phx.gbl...
>" 00ScarlettJohnson" <EE@.yahoo.com> wrote in message
>news:ekXwbLCcHHA.2552@.TK2MSFTNGP06.phx.gbl...
> Sounds like source database may be using nvarchar for its columns?
> Probably need to cast them (and possibly lose unicode data, but sounds
> like you have none) before you export them.
>
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com
> http://www.greenms.com/sqlserver.html
>|||Can anyone please help? Is this the correct group I post this kind of
question? Thanks.
" 00ScarlettJohnson" <EE@.yahoo.com> wrote in message
news:OgwAMpQcHHA.588@.TK2MSFTNGP06.phx.gbl...
>I solved the problem by adding data conversion task between source and
>destination. But this does only for append. How can I do it for overwrite?
>Thanks.
>
> "Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in
> message news:OVMWf4OcHHA.4260@.TK2MSFTNGP02.phx.gbl...
>|||Hello 00ScarlettJohnson,

> Can anyone please help? Is this the correct group I post this kind of
> question? Thanks.
I'll try; No, please use "microsoft.public.sqlserver.integrationsvcs" and
I'm wondering if you mean by "overwrite" that you want it to have the data-c
onverted
columns have the same names, yes you can do that but note you will still
be generating a new lineage for the converted column and all of the overhead
associated with that.
Thanks!
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/

export a table

I tried to write a package for transferring SQL 2005 table to a flat file in
Visual Studio. However I got the unicode error message at the destination
even though I only use English. Does anyone has idea? Thanks.
The message is as following :
Error: Column "Status" cannot convert between unicode and non-unicode
string data types.
Error: ... ( The same message with all the column in the source table)
Please help. Thanks." 00ScarlettJohnson" <EE@.yahoo.com> wrote in message
news:ekXwbLCcHHA.2552@.TK2MSFTNGP06.phx.gbl...
>I tried to write a package for transferring SQL 2005 table to a flat file
>in
> Visual Studio. However I got the unicode error message at the destination
> even though I only use English. Does anyone has idea? Thanks.
> The message is as following :
> Error: Column "Status" cannot convert between unicode and non-unicode
> string data types.
> Error: ... ( The same message with all the column in the source table)
> Please help. Thanks.
>|||" 00ScarlettJohnson" <EE@.yahoo.com> wrote in message
news:ekXwbLCcHHA.2552@.TK2MSFTNGP06.phx.gbl...
>I tried to write a package for transferring SQL 2005 table to a flat file
>in
> Visual Studio. However I got the unicode error message at the destination
> even though I only use English. Does anyone has idea? Thanks.
>
Sounds like source database may be using nvarchar for its columns?
Probably need to cast them (and possibly lose unicode data, but sounds like
you have none) before you export them.
> The message is as following :
> Error: Column "Status" cannot convert between unicode and non-unicode
> string data types.
> Error: ... ( The same message with all the column in the source table)
> Please help. Thanks.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||I solved the problem by adding data conversion task between source and
destination. But this does only for append. How can I do it for overwrite?
Thanks.
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:OVMWf4OcHHA.4260@.TK2MSFTNGP02.phx.gbl...
>" 00ScarlettJohnson" <EE@.yahoo.com> wrote in message
>news:ekXwbLCcHHA.2552@.TK2MSFTNGP06.phx.gbl...
>>I tried to write a package for transferring SQL 2005 table to a flat file
>>in
>> Visual Studio. However I got the unicode error message at the destination
>> even though I only use English. Does anyone has idea? Thanks.
> Sounds like source database may be using nvarchar for its columns?
> Probably need to cast them (and possibly lose unicode data, but sounds
> like you have none) before you export them.
>
>> The message is as following :
>> Error: Column "Status" cannot convert between unicode and non-unicode
>> string data types.
>> Error: ... ( The same message with all the column in the source table)
>> Please help. Thanks.
>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com
> http://www.greenms.com/sqlserver.html
>|||Can anyone please help? Is this the correct group I post this kind of
question? Thanks.
" 00ScarlettJohnson" <EE@.yahoo.com> wrote in message
news:OgwAMpQcHHA.588@.TK2MSFTNGP06.phx.gbl...
>I solved the problem by adding data conversion task between source and
>destination. But this does only for append. How can I do it for overwrite?
>Thanks.
>
> "Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in
> message news:OVMWf4OcHHA.4260@.TK2MSFTNGP02.phx.gbl...
>>" 00ScarlettJohnson" <EE@.yahoo.com> wrote in message
>>news:ekXwbLCcHHA.2552@.TK2MSFTNGP06.phx.gbl...
>>I tried to write a package for transferring SQL 2005 table to a flat file
>>in
>> Visual Studio. However I got the unicode error message at the
>> destination
>> even though I only use English. Does anyone has idea? Thanks.
>>
>> Sounds like source database may be using nvarchar for its columns?
>> Probably need to cast them (and possibly lose unicode data, but sounds
>> like you have none) before you export them.
>>
>> The message is as following :
>> Error: Column "Status" cannot convert between unicode and non-unicode
>> string data types.
>> Error: ... ( The same message with all the column in the source table)
>> Please help. Thanks.
>>
>>
>> --
>> Greg Moore
>> SQL Server DBA Consulting Remote and Onsite available!
>> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>>
>