Pranav Shah on 27 Mar 2018 22:10:36
Allow "Named" Connections in Gateway. This way we don't need to change the connections when moving from Dev to Prod.
Example:
Assume I build a report and am testing it through my test Gateway and test database (DB_TEST).
Now I want to start using my Prod Gateway and use the Prod database(DB_Prod).
Currently I need to change the DB Connection in all the reports to DB_Prod to start using Prod.
It would be simpler, if the connection was not based on the Database directly, but based on the names in Gateway.
Then Test Gateway would have a connection named DB pointing to "DB_Test", Prod Gateway would have the same named connection named DB pointing to "DB_Prod".
The way this would work is that first you try to identify the connection by Gateway name, if you are in Desktop, then you try connecting to the DB directly.
- Comments (1)
RE: Named Databse connection in Gateway
While it's not quite the same as this request, one way of achieving a similar end is to use parameters in the dataset to abstract out connection string components. In my case, we parameterize the SQL Server name and database name. Then when publishing or reconfiguring the dataset,I set the parameter values as needed for the right server and map to a pre-existing datasource on a gateway. It's not too much effort, so long as you don't have too many different datasets.