As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
Is there a way to enforce MSSQL adapter to not use UNICODE format in queries? We have WF Reporting Server on Unix environment, version 8.2.03.
Right now in fex there is: WHERE Name EQ 'Star';
The query looks like this: WHERE Name = N'Star' but I want it to be like this: WHERE Name = 'Star'This message has been edited. Last edited by: FP Mod Chuck,
WebFOCUS 8.2.XX
Posts: 23 | Location: Europe | Registered: November 28, 2014
Well that's unfortunate. You might want to start looking at your DB collation and the JVM encoding and DB encoding. All of those will have some impact on if that parameter will be ignored.
In my case, the DB is set to ASCII and not UNICODE. To that end, I was generating a crap load of deadlocks on DB writes. The parameter fixed my problem write up.
"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott
Adapter MS SQL Server JDBC (because system is running on Linux), but we have also ODBC on our test version. Same issue there. We plan to move the production also to ODBC as soon as possible. SQL Server version = SQL Server 2008 R2 DB collation = Latin1_General_100_CI_AS DB encoding = 1252 Codepage = Latin1
JVM encoding is utf-8
WebFOCUS 8.2.XX
Posts: 23 | Location: Europe | Registered: November 28, 2014