I have programmed a disk catalog software in 2007 and had been using since then, this software records and stores all the disks file structure information. The software works with 3 table and only one table among them is of talk able size. this table contains the information on all the files and folder, it indexed about 50-60 DVDs, that’s nearly 66k+ rows of data, each row of data contains 8 fields of text, 1 field of bool and 2 fields of date and time. The entire file size has reached 143MB, don’t you think it is too much for a save file?.
Hence, I started to work on MS SQL database, this time for a slight advancement, I worked with Silverlight. I copied all the records from the MS Access DB to the new MS SQL DB, the functionality is mostly common, Silverlight gave a good boost to the visual aids. the new MS SQL DB, in addition, it also indexed my 2TB HDD, that’s nearly double the records, i.e. the new MS SQL Database contains nearly double, i.e. 132K+ rows. The best part is the file size, the ACCESS with half the content takes 143MB where as SQL took only 29MB with huge data.
Hence forth, I would suggest that SQL takes less space than the Access and SQL is faster than the ACCESS at providing data for more than one user. However, later I tried the compact and repair option available in Access, the size of the shrined to 30MB, sql can support many users at once and is better for mass usage unlike access, access is suited when the DB is limited to small/less use.
Those who want to use my software, please find the link here:
A small pic of it reading my 2TB HDD is here:
Please feel free to use the software and only request is to let me know if there are any issues/bugs with it.
No comments:
Post a Comment