Hey John -
I'm trying to find some common ground here, help me out . I'm not disagreeing with you, I'm trying to explain why what is you see is what you see.
Let me come at this from a different way. I want to make sure you understand what I'm trying to say (I also understand you won't like it - neither do I, actually).
When it comes to data source creation / editing, there has never been parity between Desktop and Server...for any data source...not just Oracle. The dialogs in Desktop are specific to the driver being utilized. If you open up the Oracle vs. SQL Server v. Postgres connection dialogs, you're going to see different stuff in different places based on what the driver needs.
In Server, the edit connections dialog is completely generic. Always has been. Above and beyond (I think, anyway) a connection to a web-service based data source like Google Analytics or SalesForce, it's going to be the same dialog every time regardless of what your back-end is. Not good, right? Right. But it's been good enough for most people thus far. I did a quick search and this idea seems to be the closest thing to what you're asking about, but it's still not the same thing. That's why I suggested you throw an Idea out on the Idea forums - let people vote on the exact scenario you're thinking about.
Anyway, I can tell you're frustrated. Sorry. I think I've done all I can do in terms of trying to explain what the situation is, so I'm going to move on.
john liptak wrote:
I disagree completely. Your comment suggests that you rarely use Tableau to connect to oracle or you are just upset that that someone is telling it like it is. This is important to every user of Tableau that connects to Oracle.
It's totally cool to disagree but on the flip-side I have users that use Oracle every day and we don't have this issue at all. Although, our DBAs plan things very well and don't go changing stuff because much more is affected than "just reporting".
john liptak wrote:
Don't underestimate the need for this just because people don't post in your forums. People will always find work-arounds.
When there is a problem it cannot be solved unless it is exposed. Of course people will find work-arounds, that's what makes humans such great tool makers Russell has given you a good way to let Tableau know about a weakness. This is how it works here and it works fairly well. This is our house and our rules.
john liptak wrote:
This is a BASIC feature of an oracle connection string. Has been for a very long time.
It doesn't matter if it's a basic feature or not, that is not relevant, that is your opinion.
john liptak wrote:I don't even know why I'm having this discussion with you. ...
It's because he's trying to convey to you why the software does what it does. You may not like the answer but then you did ask so...
Russell Christopher wrote:
Thanks for going out of your way to find that, I up-voted it.
It's not pretty, but I have found a manual method to do this.
Download the workbook, convert to zip file.
Extract the underlying tds
open in an xml editor (I use Visual Studio)
Change authentication line 'service' parameter and any other fields you may need.
<connection authentication='MyConnectionName' class='oracle' one-time-sql='' port='<port>' schema='<schema>' server='<server>' server-oauth='' service='<service>' username='<UserName>' workgroup-auth-mode='prompt' />
Save and open the tds file.
Login with password and republish to Tableau server.
Note: if you change the <schema> parameter, you probably will need to do a 'Find and replace all' type function because it appears for every table.
ex: <relation connection='Blah_leaf' name='SomeName' table='[<schema>].[<TableName>]' type='table' />
I have a console app that does the find and replace all, so I can do them in bulk.
It's a workaround, but it fills the gap because now you don't have to replace every table in the connection via the UI.
brutal -- we just migrated to an AWS Oracle source and I have to update hundreds of connections.
It is brutal. They should build this into the UI. I have to go through this for every analysis I make for prod and qa environments.
It is appalling to see how an argument in favor of classifying this clear limitation as an over-sighted product limitation is being passed as mere "opinion".
As the original poster rightly said the server version of TABLEAU costs fortune. TABLEAU should have spent good amount of effort to come to conclusion that probability of Oracle service/sid_name change is as good as change of ServerHost and Port .