RE: String truncation in insert to SQL Server with DBD::ADO and p lace holders

From: Vahe - NC Sarkissian (Vahe.Sarkissian_at_cnb.com)
Date: 09/20/04 

To: "ZIGLIO, Frediano, VF-IT" <Frediano.Ziglio@vodafone.com>, Steffen Goeldner <sgoeldner@cpan.org>
Date: Mon, 20 Sep 2004 08:14:40 -0700

I upgraded MDAC to 2.8 before I posted the first message. I got it from
http://msdn.microsoft.com/data. Unless there's a more recent version that
I'm not aware of, I don't think the bug's in the MDAC layer.

Sadly, I think Steffen's suggestion is the best one.... Possibly you could
add a test for it, and make a note of it in the POD. I think that's all
that's practical.

Thank you both.
--Vahe

-----Original Message-----
From: ZIGLIO, Frediano, VF-IT [mailto:Frediano.Ziglio@vodafone.com]
Sent: Monday, September 20, 2004 3:51 AM
To: Steffen Goeldner; Sarkissian, Vahe - NC
Cc: dbi-users@perl.org
Subject: RE: String truncation in insert to SQL Server with DBD::ADO and
place holders

>
> Steffen Goeldner wrote:
>
> > Mysterious! Looks like the first execute establishes
> > a sticky max. length in SQL Server.
>
> Indeed, I can reproduce it with pure ADO (see attached script).
> Unfortunately, I don't see a portable workaround for DBD::ADO. I think
> it would be best the SQL Server team buys a Shared Source License from
> the Access or FoxPro team - they know how to do it ;-)
>
>
> Steffen
>

Try to update your MDAC. It should be fixed in recent versions (ODBC had the
same problem, DBD::ODBC tests contains this check)

freddy77

Relevant Pages

  • Re: Sql Server Agent (2000) erroring out on DTS Packages
    ... DTSRun: Package execution complete. ... and a problem with a missing MDAC dll. ... On Sql Server 7, this was SQLAgentCmdExec. ... Specified driver could not be loaded due to system error 126 (MERANT MSSS ...
    (microsoft.public.sqlserver.dts)
  • Re: Any help here???
    ... > start looking for things that are non standard (like having MDAC installed). ... > Format your drive, do a new/clean install of XP, and go from there. ... >>> data provider is optimized for SQL Server. ... >>> I've never had any SQL Server connectivity problems since I've switch to ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: SQL server Login connection failed sqlstate 28000 sql server e
    ... mdac 2.8 - ran the mdac checker and everything is fine ... and reconnect to the sql server using odbc - dsn connection. ... Now when we make mods to the database, reconnect, then we get that error. ... please download Component Checker from the link below to make sure ...
    (microsoft.public.sqlserver.odbc)
  • Re: Help Please Wit Error
    ... Occasionally I receive the error you are mentioning when the SQL Server ... I have had to completely remove the MDAC and re-install it as well ... see an example of the connection string you are using. ... Please install Microsoft Data Access Components ...
    (microsoft.public.dotnet.csharp.general)
  • Re: connect to named instances
    ... 'MDAC Utility: Component Checker' ... SQL Server MVP ... >> port number with any MDAC version if it makes you more comfortable. ... >> Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.server)