Re: 900 byte limit on stored procedure parameter?
- From: "Tony Rogerson" <tonyrogerson@xxxxxxxxxxxxxxxx>
- Date: Fri, 7 Apr 2006 16:12:01 +0100
Please post the stored procedure and the full CREATE TABLE definition -
including indexes, constraints etc...
Tony
--
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"ZRexRider" <jerryg@xxxxxxx> wrote in message
news:1144415792.035582.134890@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
I have a .NET application that I want to save the Config.EXE contents
to my SQL database for remote review/testing. This config file is
3700+ bytes long. I created a field in one of my tables with a VARCHAR
4800 and then created a stored procedure that receives a parameter
(also VARCHAR(4800).
However it fails to write anything if the length of the value that I
pass is anything greater than 900. If I pass exactly 900 characters or
less - the data is written to the field. If I pass 901 characters I
get nothing.
I'm suspicious since it is exactly 900. I seriously doubt it's some
limitation of MS-SQL so I need a nudge in the right direction.
Thanks
.
- Follow-Ups:
- Re: 900 byte limit on stored procedure parameter?
- From: ZRexRider
- Re: 900 byte limit on stored procedure parameter?
- References:
- Help: 900 byte limit on stored procedure parameter?
- From: ZRexRider
- Help: 900 byte limit on stored procedure parameter?
- Prev by Date: Re: Maximum number of records per second that can be inserted into SQLServer 2000.
- Next by Date: Re: Row Numbers for a View
- Previous by thread: Re: Help: 900 byte limit on stored procedure parameter?
- Next by thread: Re: 900 byte limit on stored procedure parameter?
- Index(es):