Compress Access databases on webpages

The database provided to the customer many years ago uses access. It has been growing very large for two years, with a size of 1 GB. As you constantly add and update data and change the database design, database files will become larger and larger. The factors that cause the increase include not only new data, but also the performance of database files that are constantly filled with temporary and deleted objects.

The database provided to the customer many years ago uses access. It has been growing very large for two years, with a size of 1 GB. As you constantly add and update data and change the database design, database files will become larger and larger. The factors that cause the increase include not only new data, but also the performance of database files that are constantly filled with temporary and deleted objects.

The database provided to the customer many years ago uses access. It has been growing very large for two years, with a size of 1 GB. As you constantly add and update data and change the database design, database files will become larger and larger. The factors that lead to the increase include not only new data, but also the performance of database files gradually decreases as temporary objects and deleted objects are constantly filled in. The symptoms include: the object may be opened more slowly, and the query may be longer than normal, and a variety of Typical operations usually seem to require a longer time.

Therefore, it is imperative to compress the access database.

I am really worried. If you accidentally break it down, it will not be saved. Fortunately, it is very easy to back up an access database. just copy the file and solve it. You can even write An aspx webpage to execute this action, so that I can use the webpage for backup wherever I have a network, even if I use iPad, iPhone, android phones. Although it's just a big question, it's only two or three times a year. However, if you don't want customers to worry about it, you will feel the trust of them when you do these insurance tasks. Even if it is not automated by computers, at least it is automated by me!

However, only backup is not enough. Backup only solves the first step of Failure Recovery. Next, we are faced with an increasing number of old data. If we do not delete the old data, the archives will become larger and larger, and the query time will become longer and longer. This is really a waste of time. Therefore, the function of deleting old data is completed. However, this produces another dissatisfaction. Although the data is deleted and the query speed is fast, the size of the data file remains the same. It's really unpleasant to think about it.

With office access, you can open mdb and then compress the database in the master function (upper-left window)> Manage> compress and restore the database.

To do this, we need to do it manually. And you have to prepare a computer with MS access.

Of course, this work can also be done with instructions, but still need to execute instructions in a computer with MS access, and then run with the work scheduler (refer ).

C: Program Files (x86) Microsoft OfficeOffice12MSACCESS. EXE c: Northwind. mdb/compact

If you want to use a web page for execution, it will be unable to be executed due to some restrictions. This is probably because MSACCESS.exe is a desktop program. It gets stuck after execution and does not finish the work. This should be a set problem because it can be used normally in the development environment. However, in the IIS environment, it is stuck. Someone warned that the service program may not interact with the desktop, causing problems (refer ). I tried this method but it also failed. We have tried it before. If it is a console program, it can be successfully executed.

In order to insist on using web page execution, a dao will be installed in Microsoft's development environment for a long time. It is just a dll. Copy dao. dll in the bin and reference it. You only need to use two lines.

Dao. DBEngine dbe = new DBEngine ();

Dbe. CompactDatabase (target_uncompact, target_compact, null, null );

If the boss asks why two lines of programs are written for two weeks ......, Please ask Cao's good friend to answer the question.