Forum Discussion
Best practice - Sql server Source
These are couple of important points to be followed.
1. Better to do all the aggregations in sql server before loading the data in the power bi
2. Power query can do all sort of transformations, but its best to do all data manipulations at sql end.
3. Create a view instead of pulling data directly from tables. This will avoid any changes on pbix (joins, aggregations, range, where clause etc) once deployed.
4. Parametrize the server name, database name and schema name to avoid multiple time changes
Thanks,
Pallavi
These are couple of important points to be followed.
1. Better to do all the aggregations in sql server before loading the data in the power bi
2. Power query can do all sort of transformations, but its best to do all data manipulations at sql end.
3. Create a view instead of pulling data directly from tables. This will avoid any changes on pbix (joins, aggregations, range, where clause etc) once deployed.
4. Parametrize the server name, database name and schema name to avoid multiple time changes
Thanks,
Pallavi