Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
nerra
Helper II
Helper II

Apply parameters to existing dataset

HI All,

 

I have an inherited dataset with an ODBC connection to Redshift defined for the data source. 

I get an error when I change the actual server name and database name to the parameters "servername" and "database" 

Driver={Amazon Redshift (x64)}; Server=servername; Database=database;Port=5439

 

The parameters are of type Text, List of values.

What might caused it?

nerra_0-1626964470306.png

 

Also, it asks me for a gateway, but it keeps pointing to the wrong one. do I need to define a username and pwd paremeters as well? 

 

Ultimatevly, I would liek to deploy the dataset from Test to Prod by Deployment pipelines.

 

Regards,

Nerra

 

 

 

1 ACCEPTED SOLUTION
lbendlin
Super User
Super User

ODBC{"connectionstring":"dsn=" & DSNName }

View solution in original post

10 REPLIES 10
lbendlin
Super User
Super User

ODBC{"connectionstring":"dsn=" & DSNName }

@lbendlin thank you for your patientce and for walking me through this.

Kind regards,

Nerra

lbendlin
Super User
Super User

It has to be exactly the same DSN definition as you do on your desktop. 

 

Hint:  You can export your definitions from your registry, give it to the gateway admin, and they can import it into the registry on all cluster members.

 

Yes, you can store the username and password.  Remember that only report developers have access to the gateway connections, and that they have to authenticate again anyway in order to use the connections.  The only issue would be if your gateway user credentials have a wider schema than the developer user credentials. In that case you need to create multiple DSNs, one per schema.

HI @lbendlin 

 

OK. I've done that. 

But, when I try to set up ODBC{"connectionstring":"dsn=amazon redshift tb qa"} to ODBC{"connectionstring":"dsn=DSNName"} where DSNName is the parameter, it doesn't work?

 

Any suggestions?

Regards,

Nera

lbendlin
Super User
Super User

yes, the system dsn needs to be added to every gateway cluster member.

HI @lbendlin ,

 

When our Gateway admin adds the DSN to the gateway, does it have to be a DSN Name from my machine or the servername? Or does he need to create a DSN on the machine where the Gateway is running?

And, should I also store Username & PWD in parameters? Is that considered safe?

 

Regards,

Nerra

lbendlin
Super User
Super User

For testing try using a dsn based ODBC connection. It is easier to troubleshoot.

HI ,

 

How will this affect when we're using gateways?

I created a System DSN pointing to QA and another one pointing to PROD on my local machine.

My parameter is now the name of the System DSN. It works locally. 

 Does this System DNS need to be added to the Gateway?

 

Regards,

Nera

lbendlin
Super User
Super User

Please verify that you spelled the parameters correctly. They are case sensitive.

HI,

 

yes. I'm confirming.

nerra_0-1627300956386.png

 

Kind regards,

Nerra

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.