Versions affected: All DSP / ADM / ISA
Issue statement:
Collect users sometimes find that the [RECORD COUNT] value is 0 for every Table registered in a particular Target, yet clicking the ‘View Data’ icon reveals that rows were extracted.
Explanation / Cause:
After a ‘Refresh’ completes in Collect, a procedure fires to identify the number of rows in the Target database’s table and then update the [RECORD COUNT] value on the table registration in Collect that was ‘Refreshed’. This procedure will not find any rows if the [Server Address] of the Target data source is not an exact match for the [Server Address] of the CranSoft data source.
Resolution:
Adjust the [Server Address] of the Target data source to be a verbatim match of the [Server Address] of the CranSoft data source. (Note, the Server Address value of all DSP databases must be the same to avoid issues.)
See the screenshots below for illustration of this issue.
Collect Target (Collect -> Targets page)
Target data source (Admin -> Data Sources -> {vertical} page)
CranSoft data source (Admin -> Data Sources -> {vertical} page)
To solve the problem, the dgSAP data source’s [Server Address] should be changed to “10.40.50.145”.
NOTE: Even though “vm-support-66” resolves to the same SQL Server as “10.40.50.145”, the Record Counts will be 0 for every Table registered in the dgSAP Target in Collect.