Chat now with support
Chat with Support

Enterprise Reporter 3.5.1 - Installation and Deployment Guide

Product Overview Installation Considerations for Enterprise Reporter Installing and Configuring Enterprise Reporter Managing Your Enterprise Reporter Deployment Troubleshooting Issues with Enterprise Reporter Appendix: Database Content Wizard Appendix: Encryption Key Manager Appendix: Log Viewer

Merging Two Enterprise Reporter Databases

This section provides details about the Merge task.

 
* 
CAUTION: It is strongly recommended that you back up your databases before starting the merge. You can restore the backup if there are issues with the merge.

Syntax

Start-ERMerge [-SourceSqlHost] <string> [-SourceDatabaseName] <string>
[[-SourceUserID] <string>] [[-SourcePassword] <string>] [-TargetSqlHost] <string>
[-TargetDatabaseName] <string> [[-TargetUserID] <string>] [[-TargetPassword] <string>] [<CommonParameters>]

Parameters

•
[-SourceSqlHost] is the name of the SQL Server that holds the source database to be merged.
•
[-SourceDatabaseName] is the name of the database containing the data that will be moved in the merge.
•
[-SourceUserID] (optional) is the SQL Server user ID used to connect to the source database. If not provided, Windows credentials are used.
•
[-SourcePassword] (optional) is the SQL Server a to the source database. If not provided, Windows credentials are used.
•
[-TargetSqlHost] is the name of the SQL Server that holds the target database.
•
[-TargetDatabaseName] is the name of the database that will contain the merged data.
•
[-TargetUserID] (optional) is the SQL Server user ID used to connect to the target database. If not provided, Windows credentials are used.
•
[-TargetPassword] (optional) is the SQL Server password to the target database. If not provided, Windows credentials are used.
To merge two databases using Windows authentication
•
Provide values for SourceSqlHost, SourceDatabaseName, TargetSqlHost and TargetDatabaseName.
Start-ERMerge –SourceSqlHost Sample.Sql.Server –SourceDatabaseName SourceDatabase –TargetSqlHost TargetSample.Sql.Server –TargetDatabaseName TargetDatabase
To merge two databases using SQL Server authentication
•
Provide values for SourceSqlHost, SourceDatabaseName, SourceUserID, SourcePassword, TargetSqlHost, TargetDatabaseName, TargetUserID and TargetPassword.
Start-ERMerge –SourceSqlHost Sample.Sql.Server –SourceDatabaseName SourceDatabase –SourceUserID TestUser –SourcePassword fee3td
–TargetSqlHost TargetSample.Sql.Server –TargetDatabaseName TargetDatabase –TargetUserId TargetUser –TargetPassword fhfsk8

Restoring an Enterprise Reporter Database

This section provides details about the Restore task.

Syntax

Start-ERRestore [-TargetSqlHost] <string> [-TargetDatabaseName] <string>
[[-TargetUserID] <string>][[-TargetPassword] <string>] [-FilePath] <string>
[-Password] <string> [<CommonParameters>]

Parameters

•
[-TargetSqlHost] is the name of the SQL Server that holds the target database.
•
[-TargetDatabaseName] is the name of the database that the restore task will populate with restored data.
•
[-TargetUserID] (optional) is the SQL Server user ID used to connect to the target database. If not provided, Windows credentials are used.
•
[-TargetPassword] (optional) The SQL Server password to the target database. If not provided, Windows credentials are used.
•
[-FilePath] is the full path to the backup .erbackup file, including the file name with file extension.
Example: C:\Users\Jane\Desktop\BackupFile.erbackup
•
[-Password] is the password that was be used to encrypt the backup file and is now required to access the file during the restore process.
To restore a database using Windows authentication
•
Provide values for TargetSqlHost, TargetDatabaseName. FilePath, and Password.
Start-ERRestore –TargetSqlHost Sample.Sql.Server –TargetDatabaseName RestoreDB –FilePath C:\Users\Bob\Documents\TestDB –Password 77dhw
To restore a database using SQL Server authentication
•
Provide values for TargetSqlHost, TargetDatabaseName, TargetUserID, and TargetPassword.
Start-ERRestore –TargetSqlHost Sample.Sql.Server –TargetDatabaseName RestoreDB –TargetUserId TestUser –FilePath fee3td –FilePath C:\Users\Bob\Documents\TestDB –Password 77dhw

Transferring an Enterprise Reporter Database

This section provides details about the Transfer task.

Syntax

Start-ERTransfer [-SourceSqlHost] <string> [[-SourceDatabaseName] <string>]
[[-SourceUserID] <string>][[-SourcePassword] <string>] [-TargetSqlHost] <string>
[-TargetDatabaseName] <string> [[-TargetUserID] <string>] [[-TargetPassword] <string>] [-SelectedOptions] <TransferDataSelectionEnum>
{None | ClustersAndNodes | Discoveries | Reports} [<CommonParameters>]

Parameters

•
[-SourceSqlHost] is the name of the SQL Server that holds the source database.
•
[-SourceDatabaseName] is the name of the database containing the data that will be transferred into a clean target database.
•
[-SourceUserID] (optional) is the SQL Server user ID used to connect to the source database. If not provided, Windows credentials are used.
•
[-SourcePassword] (optional) is the SQL Server password to the source database. If not provided, Windows credentials are used.
•
[-TargetSqlHost] is the name of the SQL Server that holds the target database.
•
[-TargetDatabaseName] is the name of the database that the data will contain the transferred data.
•
[-TargetUserID] (optional) is the SQL Server user ID used to connect to the target database. If not provided, Windows credentials are used.
•
[-TargetPassword] (optional) is the SQL Server password to the target database. If not provided, Windows credentials are used.
•
[-SelectedOptions] are the three choices of data to transfer in any combination. You may specify each data type using its name or numerical equivalent. ClustersAndNodes (or 1), Discoveries (or 2), and Reports (or 4).
To transfer clusters and nodes, discoveries and reports using Windows authentication
•
Provide values for SourceSqlHost, SourceDatabaseName, TargetSqlHost, TargetDatabaseName. and SelectedOptions.
Start-ERTransfer –SourceSqlHost Sample.Sql.Server –SourceDatabaseName SourceDatabase –TargetSqlHost TargetSample.Sql.Server –TargetDatabaseName TargetDatabase –SelectedOptions 1, 2, 4
To transfer clusters and nodes, discoveries and reports using SQL server authentication
•
Provide values for SourceSqlHost, SourceDatabaseName, SourceUserID, SourcePassword, TargetSqlHost, TargetDatabaseName, TargetUserID and TargetPassword.

Start-ERMerge –SourceSqlHost Sample.Sql.Server –SourceDatabaseName SourceDatabase –SourceUserID TestUser –SourcePassword fee3td
–TargetSqlHost TargetSample.Sql.Server –TargetDatabaseName TargetDatabase –TargetUserId TargetUser –TargetPassword fhfsk8 –SelectedOptions ClustersAndNodes, Discoveries, Reports

Appendix: Encryption Key Manager

•
Starting the Encryption Key Manager
•
Generating a key file
•
Importing a key file
•
Exporting a key file
•
Resetting credentials

Enterprise Reporter makes use of FIPS 140-2 compliant encryption to secure user credentials and includes an encryption key management tool. The Enterprise Reporter Encryption Key Manager can be started from the Windows Start menu. This tool allows you to perform the following tasks related to the Enterprise Reporter encryption key.

•
Generating an encryption key
•
Importing an encryption key from a backup file
•
Exporting an encryption key to a backup file
•
Resetting Enterprise Reporter user credentials
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating