Help: 900 byte limit on stored procedure parameter?

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

.

Relevant Pages

  • Re: {S} I cant believe I fell for that
    ... abilities. ... nuking the config file. ... I've just noticed that with one of my characters I can consistently ...
    (rec.games.roguelike.angband)
  • Re: UTF8 strings and filesystem access
    ... contain any non-ASCII characters) ... Then why is it a wide string? ... It's read in using XML::Simple from a config file that does not ...
    (comp.lang.perl.misc)
  • Re: The need to get around the 4000 character limit in varchar2
    ... The SQL database has a few columns that are varchar columns, ... At this point I know of no way to migrate this data across to Oracle ... to change the column you are migrating from back to 4000 characters. ...
    (comp.databases.oracle.server)
  • Re: cant insert cyrillic or greek charachters into mssql db
    ... anmssqldatabase -field is nvarchar- i only see ??? ... incorrect characters. ... Showing the Characters in the Browser is no problem, ... Sounds like you need to be looking for help in an MS SQL database newsgroup. ...
    (comp.lang.php)
  • Re: problem with unicode
    ... Thus wrote tvin, ... the lenght of frédéric should be 8 to insert correctly in sql database ... You're confusing bytes and characters. ...
    (microsoft.public.dotnet.general)