|
-
Jan 19th, 2010, 11:27 PM
#1
Thread Starter
Frenzied Member
[RESOLVED] preposterous 8000 limit in SQLServer fields
Hi all,
Now first of all, I know there's lots of forum posts on this topic, however, so far all I seem to find are workarounds to the 8000 varchar limit problem. That's not what i'm looking for, I would like to do this properly and so I would like to know some information about this to which I can't seem to find on any of Microsofts resources.
Ok so actually it's not varchar that I'm using, but the 8000 limit seems to apply to any field type, I'm using a binary field but I need to know it can store more than 8000. Now Microsoft itself says the size limit of a field is something like 2.1 billion bytes (same as every other database I've used).. yet when I try to create a field, it limits me to 8000, now I'm using express edition... and what I would like to know is..
does this same limit apply to Standard and Enterprise editions?
(I know there is a TOTAL 4gb limit on express, but there doesn't seem to be mention of field size)
So if anyone has Standard or Enterprise and could be kind enough to test making a field larger than 8000(or have done it before), please could you let me know?
If the paid for editions support the proper 2.1billion or so size, then I'll simply get hold of a copy of those. If not, I'll either mess around with multiple records in SQLServer or just ditch it for another engine.
Thanks for your time
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|