Want 2 change connection 4m Dev 2 Prod before publishing to Power BI Service, What should I do 4m QE

[Anonymous]

I have two Microsoft SQL Server database servers named SQLProd1 and SQLDev1.
SQLDev1 contains the same tables as SQLProd1, but only a subset of the data in SQLProd1.
I create a new Power BI Desktop model that uses 120 tables from SQLDev1.
I plan to publish the Power BI file to the Power BI service.
I need to connect the model to the tables in SQLProd1.

The solution must minimize
administrative effort.

What should I do from Query Editor before you publish the model?

1 Configure the Data source settings.
2 Edit the source of each table query.

Please can someone explian which is right ans and why?

[Anonymous]

---

@Anonymous wrote:

I have two Microsoft SQL Server database servers named SQLProd1 and SQLDev1.
SQLDev1 contains the same tables as SQLProd1, but only a subset of the data in SQLProd1.
I create a new Power BI Desktop model that uses 120 tables from SQLDev1.
I plan to publish the Power BI file to the Power BI service.
I need to connect the model to the tables in SQLProd1.

The solution must minimize
administrative effort.

What should I do from Query Editor before you publish the model?

1 Configure the Data source settings.
2 Edit the source of each table query.

Please can someone explian which is right ans and why?

---

"Edit the source of each table query" is Right Answer 

Clue: What should you do from "Query Editor" before you publish the model?

[parry2k]

@Anonymous you should use parameters to store sql server information and then use that parameter in your query as part of source, once you are ready to publish, just change the value of parameters and all the queries will point to production server, it will be easier and quicker to switch between environments.

[Anonymous]

---

@parry2k wrote:

@Anonymousyou should use parameters to store sql server information and then use that parameter in your query as part of source, once you are ready to publish, just change the value of parameters and all the queries will point to production server, it will be easier and quicker to switch between environments.

---

Thanks for your input. Its helpful.

But still I want to know which one is right from given option..? and why?

[parry2k]

@Anonymous I already explained why using parameter is better option, not sure what other question you have.

[Anonymous]

---

@parry2k wrote:

@AnonymousI already explained why using parameter is better option, not sure what other question you have.

---

Thanks for your response. I am not challenging your idea. 

Defenetly that is best solution. 

But my question was specific and looking for ans from given options. 

Other members, please can somebody help me on this.

[parry2k]

@Anonymous any logical reason why you want to stick to only those 2 options. I'm sure there is rational behind it and would like to know. 

[Anonymous]

---

@parry2k wrote:

@Anonymousany logical reason why you want to stick to only those 2 options. I'm sure there is rational behind it and would like to know. 

---

We have a process and simply we can't modify existing production reports. We have not yet implemented parameter option and It will take time to implement and test. Looking for quick solution which should be accepted.

I hope you are satisfied now:)