Application root url
|
Enter the URL for the application web server. This is the virtual directory for the web application. Generally, the format is “http://[Server name]/[Virtual directory name].”
|
Application web service database key
|
Enter the database name that appears in the select database prompt of the application login screen
|
Hosted SiteInfoID
|
When running this utility in a hosted environment, specify the HostedSiteID in order to retrieve the list of databases associated with a site.
|
Web Service Password
|
Specify the password for the Web Service User.
|
Web Service User Name
|
Specify the user name to use when connecting to the web service. This is required if the virtual directory is configured for Basic Authentication.
|
Validate application root url
|
Select whether to validate the URL for the application web server in the Application root url field.
|
(Application SQL Server instance)
|
Enter the SQL Server instance for the application database.
|
Application database
|
Enter the name of the application database.
|
OLTP SQL Server database
|
For users with The Raiser’s Edge, enter the name of the source database for The Raiser’s Edge.
|
OLTP SQL Server instance
|
For users with The Raiser’s Edge, enter the SQL Server instance for the source database. To deploy the standard data mart, the source database must use SQL Server 2005 or higher.
|
Analysis Services database
|
For users with Blackbaud CRM, enter the name of the database for the OLAP cube.
|
Analysis Services instance
|
For users with Blackbaud CRM, enter the SQL Server instance for the OLAP database.
|
Report mart database
|
For users with Blackbaud CRM, enter the name of the database for the data mart.
|
Report mart SQL Server instance
|
For users with Blackbaud CRM, enter the SQL Server instance for the data mart.
|
Mart key
|
The data mart uses the same database as the application, and the data mart key distinguishes data mart files from other files in the database. This key appears at the beginning of tables, stored procedures, and other items in the SQL Server schema.
|
Mart manifest file
|
Enter the location of the manifest file. This is an XML file with metadata about the data mart installation that determines the information in the other fields under Deployment file. The deployment folder from the Data Mart tab contains the manifest file.
|
Mart name
|
This field displays the data mart type as it appears in the application.
For users with The Raiser’s Edge, only the standard data mart for The Raiser’s Edge is available. For users with Blackbaud CRM, only the data mart for the records in Fundraising is available.
|
OLTP Database Location
|
This field displays the location of the source database relative to the application database.
|
Report Database Location
|
This field displays the location of the report database relative to the application database.
|
Configure data mart after deployment
|
For users with Blackbaud CRM, select whether to run configuration tasks after deployment. If you set this option to False, the deployment wizard will not populate the record source fields in the application.
|
Create Database Synonyms
|
Select whether to create SQL Server synonyms for database objects. If you set this option to False, the deployment wizard will not be able to communicate between different SQL Server instances.
|
Create Report Services OLAP Data Source
|
For users with Blackbaud CRM, select whether to create a Report Services data source for the OLAP database.
|
Deploy catalog items
|
Select whether to load catalog packages included with the data mart deployment files. If you set this option to False, the deployment wizard will not install the files to make fields in the data mart available in the application.
|
Deploy Large UDM Dimensions
|
True if the deployment needs to change the caching options for very large dimensions and disable drillthroughs. This setting is needed if there will be dimensions with more than 10 million records.
|
Enable ETL job start from shell
|
Select whether to register ETL job information to allow you to start the ETL process in the application. If you set this option to False, you must start the ETL process from SQL Server.
|
Grant file and folder rights for SQLAgent SSIS job
|
Select whether to grant read rights to the SSIS packages. If you set this option to False, you must grant permissions to the SSIS packages manually for the ETL process.
|
Register data mart in application
|
Select whether to include the data mart on the Data Marts page in the application. From this page, you manage the ETL process. If you set this option to False, you must manage the ETL process from SQL Server.
|
OLAP Extensions Path
|
Optional. The path to the extend folder containing extension to the warehouse, ETL process and the cube.
|
Analysis Services deployment utility
|
For users with Blackbaud CRM, enter the path to the command line utility for the deployment of the OLAP database.
|
Report database data path
|
Enter the location to store the data files for the report database. If you do not enter a path, the default is the SQL Server data folder.
|
Report database log path
|
For users with Blackbaud CRM, enter the location to store the log files for the report database. If you do not enter a path, the default is the SQL Server data folder.
|
Local account Machine list
|
For users with The Raiser’s Edge, if you use a local machine user account to communicate between the application and the data mart’s source, enter a list of the computers where you want to synchronize the account credentials.
|
Reset Trusted Account Password
|
For users with The Raiser’s Edge, if you use a local machine user account, select whether to reset the password to the value in the Trusted Account Password field.
|
Trusted Account Is Local User
|
This field indicates whether you use a local machine user account or a domain account.
|
Trusted Account Password
|
Enter a password for the Microsoft Windows user account. The deployment wizard does not save this password. To redeploy the data mart, you must re-enter the password.
|
Trusted Account User Name
|
Enter a Microsoft Windows user account. If the account does not have rights to communicate between the application and the data mart’s source, the deployment wizard will grant the necessary rights. If you enter a local machine user account, the deployment wizard will create the account if it does not exist.
|
SSIS configuration file environment variable
|
This field displays the environment variable for the SQL Server Integration Services package configuration. This is created on your computer to facilitate the ETL process.
|
SSIS package root folder
|
Enter the location to deploy the SSIS package. By default, the deployment wizard uses the SQL Server instance to determine the location. However, if you use a clustered SQL Server environment, you can enter a Universal Naming Convention path or another path. If you do not enter a custom path, the program uses the default SQL Server path.
|
SSIS package subfolder
|
This field displays the path to the SSIS package configuration file that contains the SQL statements for the ETL process.
|
SSIS SQL Agent Job Name
|
This field displays the SQL Agent job that the deployment wizard creates to run the ETL process.
|