This article outlines the information Cognition360 requires to connect to and process data in an Azure database hosted in a Partner's environment.
Partners have the option to host the report database within their own Azure tenant, specifically
a Platform as a Service (PaaS) Azure SQL Database and not a SQL Managed Instance or SQL Server installed on a (Infrastructure as a Service (PaaS)) server within Azure.
For Cognition360 to push the Partner's data from the Cognition360 data warehouse to the self-hosted report database, we require the following information:
- Azure SQL Server Name - {servername}.database.windows.net:
- Allow Azure services and resources to access this server - Yes
- Azure SQL Database Name - as defined by the partner:
- Compute - minimum tier S3 (100 DTU's)
- Storage - minimum 250 GB
- Retention period - 7 days minimum
- SQL User Account:
- Username
- Password
- No MFA set on this SQL account
- SQL User Permissions (Report Database):
- Allow login to database
- Added to db_owner role for initial set up and deployment
- Added to Data Writer role
- Added to Data Reader role
- Granted Execute
- Granted Alter
- SQL User Permissions (Master Database):
- Added to db_owner role for initial set up and deployment
- Added to db_owner role for initial set up and deployment
| Note: Master database access is required to set up the SQL login/user that will access the database from the Power BI service; this is used to refresh the report datasets. |
Once the database is provisioned and Cognition360 has access, we'll build the Cognition360 report database schema. We'll populate reference tables with their data (e.g., date dimension).
Due to processing times being extended due to the full data load, to minimize downtime, the migration of the data to the self-hosted report database will take place over the weekend. Once all data has been transferred and cleanly processed, all reports will be redeployed with the connection set to the self-hosted report database.
Any reports in the partners Power BI tenant that aren't:
The latest version
Used for dashboard or copied reports
will be manually redeployed. This ensures the report data models remain the same and downstream reporting entities don't break. The aim is to have all reporting available for use by 8 am on the Monday after the migration weekend.