Metricus has been moved to internal Yale hosting.

Service Account: s_metricus_integra

Environment	Database Server Name	Analysis Services	FQDN	Database Name	Model Name

Environment	Database Server Name	Analysis Services	FQDN	Database Name	Model Name
Production	az-coreprddb-01	core-prd-ss02.internal.yale.edu	core-prd-ss02.internal.yale.edu	_Yale	Yale_ITSM
Test	az-coretstdb-01	az-coretstss-01	az-coretstss-01.internal.yale.edu or az-coretstss-01.yu.yale.edu	_Yale	Yale_ITSM
Development	az-coredevdb-01	az-coredevss-01	az-coredevss-01.internal.yale.edu or az-coredevss-01.yu.yale.edu	_Yale	Yale_ITSM

Access to the Metricus PowerBI site is governed by Grouper. Currently, this is governed by our team and the Reporting teams.

metricus_admin has full control over the site. The Reporting team has inherited administration rights to this group.

metricus_authors can create and publish reports to the server.

metricus_readers can view reports that have been created.

Analysis services is run on the same server as the Financial Analysis Services. Any changes done to our analysis services related operations needs to be tested for impacts to the server as a whole.

Migration Process

Database and Analysis Services Updates

Database and Analysis Services updates are completed in the development servers by Metricus consultant.
Metricus consultant verifies updates are working as expected.
Metricus consultant creates migration scripts.
Metricus consultant uses migration scripts to move the updates to the test environment.
Metricus consultant verifies updates in test environment.
Yale Service Management Team verifies updates in test environment.
Yale Service Management team creates change task for migration to production and assigns to Database Administration team. This task needs to be assigned two weeks before migration.
Yale Service Management Team attaches migration scripts to migration task.
Database Administration team uses the migration scripts to move the updates to production.
Yale Service Management Team verifies updates in the production system.

Report creation and updates

User creates reports in development instance.
User migrates report to test instance.
User verifies report data and performance.
Yale Service Management Team creates change task and assigns it to the Reporting and Analytics Service. This should be two weeks before migration.
Yale Service Management Team will attach the PBIX to the change task.
Reporting and Analytics Service will migrate the report to production.
User and Yale Service Management Team will verify report.