Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
fetlock
Starting Member
8 Posts |
Posted - 2003-02-07 : 13:51:41
|
| Any one know what "Text" type's max. size is?I've got a client's db with a field as type "text". On their admin pages, it displays the whole 8,372 characters of the content that's in the database.However, only the first 7,956 characters of that content show up on the public part of their website.:(I'm thinking it's either somehow a limitation of the field's size or type, or it's something else, like a limitation of a stored procedure??? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-02-07 : 13:54:57
|
| From BOL:"The Microsoft® SQL Server™ ntext, text, and image data types are capable of holding extremely large amounts of data (up to 2 GB) in a single value. A single data value is typically larger than can be retrieved by an application in one step; some values may be larger than the virtual memory available on the client. Therefore, special steps are usually needed to retrieve these values." |
 |
|
|
mohdowais
Sheikh of Yak Knowledge
1456 Posts |
Posted - 2003-02-07 : 14:14:08
|
| The "text" datatype is positively HUGE, and 7900 characters? even varchar can take upto 8000! i think the limitation is somewhere on the webpages, perhaps the maxlength of the textbox or any other control.OS |
 |
|
|
fetlock
Starting Member
8 Posts |
Posted - 2003-02-07 : 14:47:02
|
| Hummm!Certainly giving me something to think about!Both pages (admin & public) call the content through simple stored procedures.On the admin page, the content is displayed in a div that's ContentEditable. Neither admin nor public limit use textareas with that content.Going to keep looking for what's limiting the public page, but not limiting the admin page.... |
 |
|
|
fetlock
Starting Member
8 Posts |
Posted - 2003-02-07 : 15:03:48
|
Found it!Thank you for your help!! That line about "even varchar can take upto 8000" got me looking further....It WAS in the public page's stored procedure...it was still calling an old SP (which I didn't write, neener, neener ), which converted the field to a varchar (thus the nearly 8k limitation) inorder to replace the quotes for display on the page.All I need to do was update it to just get the field, and I took care of the quotes by running a double replace as usual.Whew. |
 |
|
|
|
|
|
|
|