That is correct you are limited to 2G. Attachments do not bloat the database like the older methods, but they will increase the size of the database proportionally to the size of the document. So if you have 2gigs of documents then it will get near 2 gigs. Those are pretty big documents if 72 are getting near 2 gigs. See what happens if you compact and repair the database. Make a copy first. So my question is do you want to redesign this so that in the future when you add a document it automatically stores the timestamp? This will take some work. But, I can give you the code so that it will automatically move the documents. Or do you just want to bandaid a fix for the current documents? I will assume you will have to backdate the "timestamp" for the existing documents. You could do that without much redesign, but would require some manual effort.
If you think you are going to be adding beyond 2 gigs of documents, then it is time to extract the documents and put them on a folder on the system (preferably a network folder). Instead of storing them in the database, you will just maintain the path to the document.
Is this something where you are adding documents often? I would look at the redesign if you really need that time stamp. If this is something where you very rarely make updates/additions then you may want to go the easier but more manual approach.
On Wed, May 28, 2014 at 5:53 PM, ka0t1c_ang3l <no_reply@yahoogroups.com> wrote:
Another question, I read someplace that a database cannot be bigger than 2GB, is that correct? If so, then this database is quickly approaching the 2GB mark, and I'm sure it's because the attachments are stored in the database.
__._,_.___
Posted by: Peter Poppe <plpoppe@gmail.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (12) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar