The server value of the Power BI dataset is visible in the status bar (bottom-right corner) when connected to the dataset from DAX Studio, as shown in the following screenshot:
Server value of Power BI dataset via DAX Studio
In the following code, the server parameter is localhost:52809. To obtain the database parameter, run the following query in DAX Studio:
SELECT
[CATALOG_NAME]
, [DATABASE_ID]
FROM $SYSTEM.DBSCHEMA_CATALOGS
Both columns will retrieve the same GUID value that can be used as the database parameter.
There are other methods of obtaining the server parameter, such as finding the process ID (PID) in Task Manager and then running netstat -anop tcp from Command Prompt to find the port associated with the PID. Connecting to the dataset from DAX Studio is more straightforward and it's assumed that experienced Power BI dataset designers will have at least a basic familiarity with DAX Studio.
The server parameter (for example, localhost:52809) can also be used to connect to the running Power BI dataset via SQL Server Profiler. This can be useful for identifying the DAX queries generated by report visuals and user interactions. Alternatively, Power BI Desktop can generate a trace file via the Enable tracing setting within the Diagnostics option (File | Options and Settings | Diagnostics).
The server parameter (for example, localhost:52809) can also be used to connect to the running Power BI dataset via SQL Server Profiler. This can be useful for identifying the DAX queries generated by report visuals and user interactions. Alternatively, Power BI Desktop can generate a trace file via the Enable tracing setting within the Diagnostics option (File | Options and Settings | Diagnostics).