Sometimes the software will prompt that the compression is successful but the log has not been reduced. This is mostly caused by the log being too large and timeout. Before compressing again, please check whether the DummyColumn table exists in the database you just compressed. If so, delete it first and then run the log clear. device. Please make sure that the name of your database has not been changed. If it has been changed, you need to manually fill in the log name before the change. Before performing any operation, please make sure you have at least db_owner permissions
Similar software
Release Notes
Software address
- Green versionCheck
- Green versionCheck
- Green versionCheck
- Green versionCheck
Dongwang Pioneer Sql Log Cleaner V1.1
Added features:
1. Automatically read local connectable database
2. Integrate Windows NT security settings
3. Allow Sql verification password to be empty
4. User login failure prompt message
5. Users without Sa permission are allowed to fill in their own database name (at least they must have db_owner permission)
6. Allow filling in the Log name
7. Self-setting connection timeout time
8. Optimize code
it works
it works
it works