Is there a way to write a SQL Query into a TXT file and execute it from PBI?

[Anonymous]

Dear PBI users, good afternoon.

Currently we are analyzing dividing the development team into front-end - UI / UX design (mostly focusing on the PBI charts , UI and overall UX) and Back-end (SQL Querying, Table optmization etc).

Esentialy the idea is to allow both teams to work on the report at the same time. The conclusion was, we would like the team to write the sql query into a TXT file and we would connect into the TXT and excute the query written on it.

Unfortunately I am not very known on this process, I know how to get the content of a txt but not to execute the written query against a database within PBI.

Would anyone have a clue how to do it?

Thank you!

[ThxAlot · Accepted solution]

I managed to apply the same mode in our team last year, i.e. we use PQ to read sql files stored in a centralized sql depository; we are able to compile sql easily.

let
    // applicable to .txt / .sql files
    Source = "C:\Users\Home\Downloads\Qry.sql",
    SqlContent = Text.Combine(Table.ToColumns(Csv.Document(File.Contents(Source))){0}, "#(lf)")
in
    SqlContent

[ThxAlot · Accepted solution]

I managed to apply the same mode in our team last year, i.e. we use PQ to read sql files stored in a centralized sql depository; we are able to compile sql easily.

let
    // applicable to .txt / .sql files
    Source = "C:\Users\Home\Downloads\Qry.sql",
    SqlContent = Text.Combine(Table.ToColumns(Csv.Document(File.Contents(Source))){0}, "#(lf)")
in
    SqlContent

[Anonymous]

Exactly what we want to do , quick question @ThxAlot , and how do you execute it?

something like a blank query with 

= Sql.Database("server", "view", [Query=SQLContent])?

[ThxAlot · Accepted solution]

Sql.Database("server", "database", [Query=SQLContent])

[Anonymous]

Amazing! Just out of curiosity, how was the development after implementing this method? Overall better?

[ThxAlot]

In terms of performance, this mode isn't better than hard-coded PQ queries; the biggest advantage is segregation; front-end and back-end devs may focus on their domain respectively.