adVarWChar slower than adVarChar
- From: "N. Scheller" <n.scheller@xxxxxxxxxxx>
- Date: Wed, 23 Aug 2006 10:31:39 +0200
Hello experts,
I have some trouble with importing UTF files into a database:
the table in which I want to import the file contains a nvarchar(200) field
on SQL2000 and a nvarchar2 field in our Oracle-DB. We have written an import
program in VB which creates a stored procedure to which all information from
the text file is passed. The parameter for the mentioned field has the same
type as the field in the DB - nvarchar(200) on MS or nvarchar2 on Ora.
Until last month, the import program used "adVarChar" to pass the values to
the SP:
cmdADO.Parameters.Append .CreateParameter(aColumnName(i), adVarChar,
adParamInput, 200)
Then we changed adVarChar to adVarWChar, since we had to import UTF files
containing special characters:
cmdADO.Parameters.Append .CreateParameter(aColumnName(i), adVarWChar,
adParamInput, 200)
Well, now we get the special characters properly imported into the table.
But the importing time for one file containing some thousand lines
increased from 8 minutes to more than 8 hours!!!
Changing back the parameter type to adVarChar, and we import the same file
in 8 minutes again.
Since we have the same odd behavior on MS-SQL and Oracle, I assume this is
an ADO problem.
Any ideas?
Thanks in advance
Norbert
.
- Follow-Ups:
- Re: adVarWChar slower than adVarChar
- From: Stephen Howe
- Re: adVarWChar slower than adVarChar
- From: Bob Barrows [MVP]
- Re: adVarWChar slower than adVarChar
- Prev by Date: Re: DataTables How to edit a Row?
- Next by Date: Re: adVarWChar slower than adVarChar
- Previous by thread: Re: DataTables How to edit a Row?
- Next by thread: Re: adVarWChar slower than adVarChar
- Index(es):
Relevant Pages
|
|