[thetech]

We are using the Licensed version of ADCR (installed 12/2008) and just upgraded to version 5.

Can I simply point the reporting configuration of my upgraded copy to the old database? Is it required that I create a new database and then import my old data from disk? I realize that the db schema may have changed in the new version, but is there an upgrade script?

Not wanting to run 2 sets of reports (pre- and post-upgrade) to get a complete history of AD, I decided to run the DB Importer. We collect data 4 times a day from about 50 domain controllers. We have about 12 GB (99,820 files) of change data on the disk collected since the original installation (12/2008).

The DB Importer is relatively slow, generates a huge log file, and systematically crashes with an out-of-memory error. I can deal with the speed and the log file, but the crashing is making this process much more interactive than it should be.

The DB Importer will run fine for about an hour (roughly 1 or 2 weeks of changes) and then crash with a System out of memory exception. At that point, the ADCR.exe process is consuming about 700 MB of RAM and the ADCR.log file is about 1 GB in size. I'm not seeing any database corruption, but the import process halts and I need to restart it. I'm on a 32-bit server with 4GB of memory. The server has about 1.5 GB of free memory at the time of the crash.

My restart process is as follow:
1. Run a report or check ADCR.log file to determine the date of the last item inserted into the database.
2. Restart DB Importer and set it to resume with the first collection on the date of the last item that was inserted into the database.

I'm expecting to have at least a few duplicate changes in the database, due to possible overlap. Does the DB Importer do any duplicate checking before inserting a change?

If I can't simply upgrade my old db, is there a tactic to get the DB Importer to work "unattended" for as long as it takes to import my 11 GB of changes?

[Brian Stern]

thetech, on 30 July 2009 - 12:52 PM, said:

We are using the Licensed version of ADCR (installed 12/2008) and just upgraded to version 5.

Can I simply point the reporting configuration of my upgraded copy to the old database? Is it required that I create a new database and then import my old data from disk? I realize that the db schema may have changed in the new version, but is there an upgrade script?

Not wanting to run 2 sets of reports (pre- and post-upgrade) to get a complete history of AD, I decided to run the DB Importer. We collect data 4 times a day from about 50 domain controllers. We have about 12 GB (99,820 files) of change data on the disk collected since the original installation (12/2008).

The DB Importer is relatively slow, generates a huge log file, and systematically crashes with an out-of-memory error. I can deal with the speed and the log file, but the crashing is making this process much more interactive than it should be.

The DB Importer will run fine for about an hour (roughly 1 or 2 weeks of changes) and then crash with a System out of memory exception. At that point, the ADCR.exe process is consuming about 700 MB of RAM and the ADCR.log file is about 1 GB in size. I'm not seeing any database corruption, but the import process halts and I need to restart it. I'm on a 32-bit server with 4GB of memory. The server has about 1.5 GB of free memory at the time of the crash.

My restart process is as follow:
1. Run a report or check ADCR.log file to determine the date of the last item inserted into the database.
2. Restart DB Importer and set it to resume with the first collection on the date of the last item that was inserted into the database.

I'm expecting to have at least a few duplicate changes in the database, due to possible overlap. Does the DB Importer do any duplicate checking before inserting a change?

If I can't simply upgrade my old db, is there a tactic to get the DB Importer to work "unattended" for as long as it takes to import my 11 GB of changes?

The answers to your questions are as follows:

Q:
Can I simply point the reporting configuration of my upgraded copy to the old database? Is it required that I create a new database and then import my old data from disk? I realize that the db schema may have changed in the new version, but is there an upgrade script?

A: You can specify your old database. The internal structure of the database will be updated automatically.

Q:
Not wanting to run 2 sets of reports (pre- and post-upgrade) to get a complete history of AD, I decided to run the DB Importer. We collect data 4 times a day from about 50 domain controllers. We have about 12 GB (99,820 files) of change data on the disk collected since the original installation (12/2008).

The DB Importer is relatively slow, generates a huge log file, and systematically crashes with an out-of-memory error. I can deal with the speed and the log file, but the crashing is making this process much more interactive than it should be.

A: AD Change Reporter 6.0.230 will resolve this issue. You can download it with the following link:

http://www2.netwrix....rfull_setup.msi

Q:
I'm expecting to have at least a few duplicate changes in the database, due to possible overlap. Does the DB Importer do any duplicate checking before inserting a change?

A: The DB Importer does not write changes that were written earlier and already exist in the data base, i.e. duplicate recording is impossible.


Q:
If I can't simply upgrade my old db, is there a tactic to get the DB Importer to work "unattended" for as long as it takes to import my 11 GB of changes?

A: Unfortunately, the product does not support “unattended” mode. But we have optimized memory usage in the version mentioned above.