• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Max File Size ?

bookem dano

Senior member
I have a puter with win 2003server and a db file that is now 32GB. I cannot add to the file because of some error. The error and the computer are not in front of me, but I am wondering if it is a file system issue.

Can win2003 be installed with a FAT32?
If it is a NTFS system, is there some setting or option that would allow it to be larger than 32GB?

The database is Advantage Database, which is one that I just now knew it existed. I'm trying to pack the file now, but thought I'd look into the file size idea.

Any suggestions?
 
FAT32 file size limit is 4GB. NTFS has no pratical file size limit, however since it is a database, databases usually have imposed limits on them (in many cases, such as SQL Server, you can up the size limit).
 
I may need to up the pagesize on the index. I can't try it now on my problem table, but the default on a non problem was 512 and I was able to change it to 8192. But I don't know if that would allow the db file to get larger.
 
This filesystem overview from Microsoft is a good reference for FAT, FAT32, and NTFS limitations on Windows.

The maximum volume size for FAT32 on Windows is 32 GB, but the maximum file size is 4 GB. So if your database is stored in a single file, you'll obviously hit the 4GB limitation much earlier.

And although I think FAT32 is technically still supported as a boot partition for Server 2003, I don't think I have EVER seen such a configuration. Running FAT32, you're sacrificing file system security, metadata consistency, etc. All of which is suicide on a production server.

And if your server is running NTFS, then you you'll run out of physical disk space before you hit any limitations.
 
That's what I thought too. I just don't have the server in front of me so I was trying to think of reasons why he is getting errors at 32 GB. I do know that the program had an issue before when the file got to be 4gb and that they rewrote the program and swore it was 'limitless'. Of course, they swore that too before the 4gb file issue came into play.

Trying to fix this for a day where the computer program's support people are not reachable.
 
Remind me not to use Advantage as a database. 🙁
Server 2003 has no problem with a file greater than 32GB in size. Many Exchange Servers have databases that size.

Here's Advantage's brochure describing the DBF sizes for Advantage 8.0

"Previously, DBFs could be no larger than 4 GB in size (2 GB in Linux prior to glibc 2.1.2 and kernel 2.4). This is still the case with 32-bit Windows operating systems using FAT32 and NetWare 5 or greater with the NSS file system.
However, with 32-bit Windows using NTFS, NetWare 5 and greater with traditional file systems, and Linux glibc 2.1.2 and kernel 2.4 and higher, the maximum size of a DBF is substantially greater. Specifically, with these operating systems a DBF can be the maximum number of records supported by DBF (2,147,483,648) multiplied times the size of each record. For example, if each record in a DBF is 1,000 bytes in size, the maximum size of that DBF would be just under two terabytes (2,147,483,648,000 bytes)."
 
Thanks for the info. I don't think that we are using 8.0 so I'll have to try to find out what it is.

I'm getting error7073 maximum number of memo blocks available has been exceeded.

I already did reindex the file but no dice.

Wehave 7.1 Advantage.
 
Back
Top