Skip to Content.
Sympa Menu

freetds - Re: Large Text and Image Files

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: Brian Bruns <camber AT ais.org>
  • To: TDS Development Group <freetds AT franklin.metalab.unc.edu>
  • Subject: Re: Large Text and Image Files
  • Date: Tue, 14 May 2002 19:02:33 -0400 (EDT)



There is a conf file setting to do this, 'text size = xxx'. The only
reason I haven't made it default (besides lack of time) is that Sybase
actually works. It's a one line change to config.c though, and hopefully
I'll apply it once I work through some pending patch sets.

Brian

On 14 May 2002, Michael Peppler wrote:

> On Tue, 2002-05-14 at 15:32, Michael Hudin wrote:
> > Okay, so I'm going crazy trying to get my Linux server to properly pull
> > out large files from the database. I'm using Redhat 7.2 with Perl 5.6.1,
> > freetds 0.53, and DBD Sybase. The system is accessing a NT 4.0 SP6 system
> > with MSSQL Server 7 SP4 on it.
> >
> > For some reason I've not been able to get the system to use TDS 7.0. It
> > seems to run fine with 4.2 (but with the aforementioned problem) but if I
> > set it 7.0 in the freetds.conf file, it simply won't pull any of the
> > information from the database at all and gives an "out of memory" error
> > which I find peculiar. Anyone know anything about this?
>
> MSSQL defaults the TEXTSIZE value to 2GB. So DBD::Sybase (and/or
> FreeTDS) when it sees a TEXT or IMAGE datatype column will get a size
> value of 2GB, and will try to allocate that much memory...
>
> You can reduce that with a
>
> $dbh->do("set textsize <some reasonable value>");
>
> Maybe FreeTDS should issue this by default to enable the normal default
> behavior of textsize set to 32k...
>
> (or maybe DBD::Sybase should do this - but this isn't necessary for
> Sybase databases...)
>
> Michael
>





Archive powered by MHonArc 2.6.24.

Top of Page