> actual file size might be 1400 bytes and the disk storage allocated is > close to twice that. As was also mentioned previously when you try to
Is the file system Fat32? The default cluster size for NTFS is 512 bytes, which means the disk space used to store a file will never be more than 511 bytes more than the actual size. Also, NTFS uses B-Tree directories (like a database) which means that load time in Explorer and the search time to open a file is very quick even when the number of files is very large. The cluster size issue also exists within a database. One of the biggest reasons I avoid using blobs is the backup issue. It is common to have a very large number of image files taking up a very large amount of space. If these files change very infrequently (new files are added frequently but the existing one are infrequently updated), it is easy to design a backup scheme that is very fast. If you store these blobs in the database, the database dump size will become very large and will take a long time to save and load. So far, no one has indicated a compelling reason to include blob data in a database in favor of a reference to the file. I am not saying I would never consider including blob data in a database, but I have never had a situation where there was any advantage to do so. Glenn Lawler ----------------------------------------------------- Home page: http://groups.yahoo.com/group/delphi-en/ To unsubscribe: [EMAIL PROTECTED] Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/delphi-en/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
