in reply to Character issue when pulling data out of MSSQL using DBI

Yes, there probably is a simple explanation.

But you haven't given us much to go on. "Short and simple" are great virtues, but not when they lead you to omit necessary information such as...

  1. What database?
  2. Where is it -- local or on another machine?
  3. How did you get "the field out of the database?"
  4. Do you have any idea how the string was encoded when it was entered into the DB?
  5. What is the encoding used on your machine?

Off the top of my head, and relying only on the extensive information (NOT!) that you provided, an encoding mismatch seems to be one possibility (among many).

If you'll read How do I post a question effectively?, On asking for help and I know what I mean. Why don't you?, you'll find some tips on how to pose a question here in a form the Monks can use to help you.

  • Comment on Re: Character issue when pulling data out of MSSQL using DBI

Replies are listed 'Best First'.
Re^2: Character issue when pulling data out of MSSQL using DBI
by bwickland (Initiate) on May 01, 2010 at 04:29 UTC

    Sorry for the brief description, i just was checking if it wasn't something obvious...

    I am using ActivePerl 5.8.8 the database is Microsoft SQL Server 2008 running on the same machine. The encoding of the particular field in question is "SQL_Latin1_General_CP1_CI_AS".

    As far as I am connecting to the database, I am using DBI v1.609 and DBD-ODBC v1.22.