Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
difference between hotfile and remote snapshot
- Thread starter slaforce
- Start date
Some of the Cognos documentation is quite acceptable and the portion on Hotfiles, Snapshots and Thumbnails in the 'Mastering Impromptu Reports'is quite clear.
You are right that both hotfiles and snapshots need to be created but it could be done using the scheduler which means they could be automatically updated in a batch style.
You refer to the catalog - hotfiles can be either be entered into a catalog or as a data source on their own for use with or without catalog data items.
Finally use such files with caution - they are not indexed, and if they are large can have a serious impact on response rate. Although having said that if used sensibly, they can make reports much more efficient. For example if I have complicated filters to extract records that are needed in a number of reports, I often create a hotfile of those records or as an index.
Simon Rouse
You are right that both hotfiles and snapshots need to be created but it could be done using the scheduler which means they could be automatically updated in a batch style.
You refer to the catalog - hotfiles can be either be entered into a catalog or as a data source on their own for use with or without catalog data items.
Finally use such files with caution - they are not indexed, and if they are large can have a serious impact on response rate. Although having said that if used sensibly, they can make reports much more efficient. For example if I have complicated filters to extract records that are needed in a number of reports, I often create a hotfile of those records or as an index.
Simon Rouse
CognosProfessional
Programmer
Remote Snapshots:
To create a remote snapshot, you run a report against the database using Request Server. Request Server then saves the results of the query as a result set in the database instead of locally.
The key differences between remote snapshots and local snapshots are as follows:
A report based on a remote snapshot does not contain any data. Instead, a reference or pointer points to the results table in the database.
A remote snapshot requires access to the database, often on a network, and so is not as portable as a local snapshot.
You must have Request Server to create the result set in the database.
Remote snapshots offer many of the same benefits as local snapshots. In addition, they can be created unattended during off-peak hours.
they are created by running a query directly on the database server, and so build much more quickly than tables built locally. As the size of the database increases, so too does the performance advantage of a remote snapshot.
where the result set is particularly large, a remote snapshot maintains a relatively small file size compared to the local snapshot, because the report does not actually contain any data.
Save Remote Snapshots as Local Snapshots
You can save a remote snapshot as a local snapshot on your computer so that you can work without a network connection when you are travelling or when you want to send the snapshot to other Impromptu users via email.
Steps
1. With the remote snapshot open, from the File menu, click Save As.
2. Specify the Save In location, and the File Name.
3. Click the Save Data with Report option, and click OK.
The snapshot is saved locally and you can modify the report.
CP![[cook]](/data/assets/smilies/cook.gif "[cook] [cook]")
To create a remote snapshot, you run a report against the database using Request Server. Request Server then saves the results of the query as a result set in the database instead of locally.
The key differences between remote snapshots and local snapshots are as follows:
A report based on a remote snapshot does not contain any data. Instead, a reference or pointer points to the results table in the database.
A remote snapshot requires access to the database, often on a network, and so is not as portable as a local snapshot.
You must have Request Server to create the result set in the database.
Remote snapshots offer many of the same benefits as local snapshots. In addition, they can be created unattended during off-peak hours.
they are created by running a query directly on the database server, and so build much more quickly than tables built locally. As the size of the database increases, so too does the performance advantage of a remote snapshot.
where the result set is particularly large, a remote snapshot maintains a relatively small file size compared to the local snapshot, because the report does not actually contain any data.
Save Remote Snapshots as Local Snapshots
You can save a remote snapshot as a local snapshot on your computer so that you can work without a network connection when you are travelling or when you want to send the snapshot to other Impromptu users via email.
Steps
1. With the remote snapshot open, from the File menu, click Save As.
2. Specify the Save In location, and the File Name.
3. Click the Save Data with Report option, and click OK.
The snapshot is saved locally and you can modify the report.
CP
- Status
Similar threads
- Locked
- Question
- Locked
- Question