...
- Create a new Insights database (e.g. "dzreporting") next to the DAM database.
Note: Make sure the Insights database has the same collation as the DAM database. - Create a new SQL server login (e.g. "insights").
You can use any authentication you want (Windows/SQL), but it should have the following properties:- Default database = "dzreporting" (database created in 1). Be sure to uncheck the "Enforce Password Policy, and select the DZreporting database under Default Database (changing it from master to DZreporting).
- Under User Mapping set "db_owner, public" for the insights database, and "db_datareader" for the DAM database.
- Unblock and unpack the database zip file into a local folder.
- Edit the file "Digizuite.Insights.DbUpgrade.exe.config" with a text-editor and change to match your setup:
- ConnectionString (use credentials created in step 2). Remember to set the Initial Catalog = dzreporting.
- DAMDatabaseName (to be typed in under "value= ")
- (Best pratice) Remember to backup the database i.e. yourdatabasename_dam before prior to step 5.
- Run the executable "Digizuite.Insights.DbUpgrade.exe" and inspect the output (optionally using the created 'log.txt').
...
The gateway is now ready for use.
Tip
If the connection fails it could be because the PowerBI Gateway Service has not started, to start the service.
Open Command Prompt as Administrator and run the following commands:
net stop PBIEgwService
net start PBIEgwService
Once the service is running your Gateway Connection should succeed.