+6We are using SQL Server 2014 deployed as 3 node cluster with 1 primary and 2 secondary. We need to connect to the READONLY secondary. To do that you the set the Application Intent=readonly
But i cannot find the parameter setting in the database connection for SQL Server.
+13Hi @rob_datavision and @rudy_v! As of FME 2018, the Application Intent property is available under the Writer Parameters, under the Advanced section:
I hope this helps!
+1Hi @rob_datavision and @rudy_v! As of FME 2018, the Application Intent property is available under the Writer Parameters, under the Advanced section:
I hope this helps!
Thanks nampreetatsafe for your suggestion. I finally upgraded and got around to trying this but it did not work.
It seems to me that the application intent needs to be set at the database connection stage. When you establish the connection in FME, there is no option for setting the application intent to read only. Hence it is not possible to get a list of tables. In the dialog in FME (in your diagram) the application intent is set after you have selected a database connection and a table. Even if I set it to Read Only before selecting the table, I still cannot select the table. I get errors telling me to set the application intent.
Am I missing something? Is there a way of setting the application intent to Read Only when the connection is made? This is how it is done in Microsoft SQL server management studio as per this link.
Any help would be very much appreciated.
Rob
+13Thanks nampreetatsafe for your suggestion. I finally upgraded and got around to trying this but it did not work.
It seems to me that the application intent needs to be set at the database connection stage. When you establish the connection in FME, there is no option for setting the application intent to read only. Hence it is not possible to get a list of tables. In the dialog in FME (in your diagram) the application intent is set after you have selected a database connection and a table. Even if I set it to Read Only before selecting the table, I still cannot select the table. I get errors telling me to set the application intent.
Am I missing something? Is there a way of setting the application intent to Read Only when the connection is made? This is how it is done in Microsoft SQL server management studio as per this link.
Any help would be very much appreciated.
Rob
Hi @rob_datavision! Sorry to hear that the database connection didn't recognized the Application Intent parameter. I've opened up a ticket for our team to investigate this (internal reference: FMEENGINE-61929) and will provide any updates on this thread.
@rudy_v, I'm curious to know if you've had any success?
+13Thanks nampreetatsafe for your suggestion. I finally upgraded and got around to trying this but it did not work.
It seems to me that the application intent needs to be set at the database connection stage. When you establish the connection in FME, there is no option for setting the application intent to read only. Hence it is not possible to get a list of tables. In the dialog in FME (in your diagram) the application intent is set after you have selected a database connection and a table. Even if I set it to Read Only before selecting the table, I still cannot select the table. I get errors telling me to set the application intent.
Am I missing something? Is there a way of setting the application intent to Read Only when the connection is made? This is how it is done in Microsoft SQL server management studio as per this link.
Any help would be very much appreciated.
Rob
Hi @rudy_v and @rob_datavision! The fix for the issue reported by @rob_datavision is now available in the latest FME 2020 Beta. Let us know if you encounter any further issues with this. Thanks again for reporting this and helping make FME even better!
+6Hi @nampreetatsafe
Yes that is fine to set it on reader level - but I want it on Database Connection settings - then all my work benches will use READONLY. We have Database Connection for Readers and some connections as writers for SQL Server.
+6Hi @nampreetatsafe ,
I have got it to work like this on database connection. APPLICATION INTENT with a space. This works well in a SqlExecutor
