|
Home > Archive > microsoft.public.sqlserver.server > August 2002 > Stored Procedure Limitation (Question)
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Stored Procedure Limitation (Question)
|
|
| Bucker 2002-08-15, 6:23 am |
| Hi
I have a web page which lists of bunch of inventory
items. When we submit to a web page to update
quantities, i need to pass the following
ReplenishID numeric
LocationID numeric
InventoryID numeric
Quantity numeric
I string together all the items like this
ReplenishID=LocationID=Invento
ryID=Quantity=@
In the stored procedure i break apart into seperate
records looking for @ symbol to identify end of record.
All this works fine with one exception. If i pass a string
greater than 4000 characters (sp limitation), the stored procedure bombs.
Anyway to get around this?
REgards
Jim
| |
| Adi Cohn 2002-08-15, 7:23 am |
| CHAR and VARCHAR types can hold up to 8000 characters. NCHAR and NVARCHAR
types can hold up to 4000 characters. TEXT and NTEXT types can hold up to
many milions characters (Sorry don't remember the exact number but it is a
theoretical limitation. You won't get there:-).
Adi
"Bucker" <jimbeauchamp@ameritech.net> wrote in message
news:vTM69.3119$2E6.930663@newssvr28.news.prodigy.com...
> Hi
>
> I have a web page which lists of bunch of inventory
> items. When we submit to a web page to update
> quantities, i need to pass the following
>
> ReplenishID numeric
> LocationID numeric
> InventoryID numeric
> Quantity numeric
>
> I string together all the items like this
> ReplenishID=LocationID=Invento
ryID=Quantity=@
>
> In the stored procedure i break apart into seperate
> records looking for @ symbol to identify end of record.
>
> All this works fine with one exception. If i pass a string
> greater than 4000 characters (sp limitation), the stored procedure bombs.
>
> Anyway to get around this?
>
> REgards
>
> Jim
>
>
| |
| kevin knudson 2002-08-15, 10:23 am |
| I believe the limitation is actually in the ODBC buffer
passed to the server, and 4k sounds abount right.
Try searching MSKB in ODBC Call Limitations.
KlK, MCSE
>-----Original Message-----
> CHAR and VARCHAR types can hold up to 8000 characters.
NCHAR and NVARCHAR
>types can hold up to 4000 characters. TEXT and NTEXT
types can hold up to
>many milions characters (Sorry don't remember the exact
number but it is a
>theoretical limitation. You won't get there:-).
>
>Adi
>
>"Bucker" <jimbeauchamp@ameritech.net> wrote in message
>news:vTM69.3119$2E6.930663@newssvr28.news.prodigy.com...
>> Hi
>>
>> I have a web page which lists of bunch of inventory
>> items. When we submit to a web page to update
>> quantities, i need to pass the following
>>
>> ReplenishID numeric
>> LocationID numeric
>> InventoryID numeric
>> Quantity numeric
>>
>> I string together all the items like this
>> ReplenishID=LocationID=Invento
ryID=Quantity=@
>>
>> In the stored procedure i break apart into seperate
>> records looking for @ symbol to identify end of record.
>>
>> All this works fine with one exception. If i pass a
string
>> greater than 4000 characters (sp limitation), the
stored procedure bombs.
>>
>> Anyway to get around this?
>>
>> REgards
>>
>> Jim
>>
>>
>
>
>.
>
|
|
|
|
|