|
Query name |
Hashed Files Non-Exclusive |
|---|---|
|
Server Asset Type |
Hashed File stage |
|
Analysis Type |
Hashed Files |
|
Description |
Identifies jobs featuring Hashed Files that are both read from and written to, but the write operation appends to previous contents instead of overwriting. |
Issue
A write operation appends to a Hashed File, rather than overwrites its contents, suggests that that particular Hashed File is not used as a transient data store (whose role finishes with the execution of a Job Sequence) but as a resource which exists over a long period of time, and whose role is to share important data between different invocations of the same Job or different Jobs.
Where these types of Hashed Files are shared between jobs (or indeed different projects), their usage cannot be fully assessed by automated Server to Parallel analysis tools.
This potentially makes these files unsuitable for conversion to a DRS-managed database table.
Actions
This helps customers…
-
Placeholder
See also