Re: Question about MAX param size when calling StoredProc

But I was using SQL 2005 :(

On Tue, May 20, 2008 at 3:12 PM, James K. Lowden <[email protected]>
wrote:

> Navdeep Shergill wrote:
> > so does that mean that using FreeTDS I can only send a max 8k param
> > lenght for Varbinary?
>
> Cf. http://msdn.microsoft.com/en-us/library/aa258271(SQL.80).aspx<http://msdn.microsoft.com/en-us/library/aa258271%28SQL.80%29.aspx>
>
> BINARY and VARBINARY types are restricted to 8000 bytes.  I am pleased to
> hear VARBINARY works as expected.
>
> Microsoft SQL Server 2000 allows stored procedures to define parameters of
> type TEXT or IMAGE.  I'd expect them to work with FreeTDS nowadays, but
> the src/dblib/rpc.c unit test, for instance, doesn't use those types.  If
> you try them, I'd be interested to hear back, either way.
>
> --jkl
>
>
> >
> > On Tue, May 20, 2008 at 5:22 AM, James K. Lowden <[email protected]>
> > wrote:
> >
> > > Navdeep Shergill wrote:
> > > > I am trying to call to call a
> > > > storedProc on a SQL2005 server that takes in a 'varbinary' field as
> > > > input paramter. The varbinary field is set up with '-1' as the
> > > > Length in the database.
> > >
> > > varbinary is the weirdest datatype in the library, perhaps on the
> > > planet. I have found places where Microsoft claims to use it, but in
> > > fact doesn't.
> > >
> > >
> > > Can I ask why you're using it?  Would TEXT/BINARY do just as well?
> _______________________________________________
> FreeTDS mailing list
> [email protected]
> http://lists.ibiblio.org/mailman/listinfo/freetds
>