A
Al Hasoob
Guest
I have a problem and don't know where to look at first.
- we have an VBA / C# application that uses DAO for accessing an MS access mdb file
- OS is Windows 10 Enterprise build 1809 X64
our sample database is about 300 mb in size
we were told to install the cumulative april Windows update KB4549949 by our IT
Then we observe a strange behavior change:
runnung a query over part of the data we notice a massive growth after installing these patches. The database grew from 300 MB to 440 MB.
The growth goes up to 2 GB without any data written to the database, just repeated data retrieval by read operations. Reaching the 2 GB limit the database is no longer accessible and has to undergo the "compress repair" in MS Access. However our application does not require MS Access to be installed.
Part of the data is taken directly with DAO recordsets, parts are retrieved by queries stored in the Access MDB.
I cannot reproduce this with MS Access itself on the mdb file or by linking a table from the source database, also not by importing data from this MDB with the SQL server data import wizard. So I need some hints where to look at.
With "compress repair" in MS Access we were able to shrink back the database to 300 MB
The second cumulative April update kb4550969 did not fix the behavior, also the insider preview of build 2004 shows the behavior.
Currently the only option for us is to roll back to the cumulative March 2020 update kb4554354
With this update the behavior is correct, reading from the MDB does NOT cause the MDB to grow.
IT architect - Terminal servers, virtualizations, SQL servers, file servers, WAN networks and closely related to software devleopment (8 years + experience in VB, C++ and script langugaes), MCP for SQL server and CCAA for Xenapp 6.5
More...
- we have an VBA / C# application that uses DAO for accessing an MS access mdb file
- OS is Windows 10 Enterprise build 1809 X64
our sample database is about 300 mb in size
we were told to install the cumulative april Windows update KB4549949 by our IT
Then we observe a strange behavior change:
runnung a query over part of the data we notice a massive growth after installing these patches. The database grew from 300 MB to 440 MB.
The growth goes up to 2 GB without any data written to the database, just repeated data retrieval by read operations. Reaching the 2 GB limit the database is no longer accessible and has to undergo the "compress repair" in MS Access. However our application does not require MS Access to be installed.
Part of the data is taken directly with DAO recordsets, parts are retrieved by queries stored in the Access MDB.
I cannot reproduce this with MS Access itself on the mdb file or by linking a table from the source database, also not by importing data from this MDB with the SQL server data import wizard. So I need some hints where to look at.
With "compress repair" in MS Access we were able to shrink back the database to 300 MB
The second cumulative April update kb4550969 did not fix the behavior, also the insider preview of build 2004 shows the behavior.
Currently the only option for us is to roll back to the cumulative March 2020 update kb4554354
With this update the behavior is correct, reading from the MDB does NOT cause the MDB to grow.
IT architect - Terminal servers, virtualizations, SQL servers, file servers, WAN networks and closely related to software devleopment (8 years + experience in VB, C++ and script langugaes), MCP for SQL server and CCAA for Xenapp 6.5
More...