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.
Most SQL Servers are installed with the Case-insensitive setting. This causes the SQL Filter in Data Migrator to pick up records when two columns are compared and one of the column contains the same string as the other but with different case. ---- We can change the so called collation in SQL with the "Collate SQL_Latin1_General_CP1_CS_AS" in the WHERE clause of the SQL statement. This changes the collation from Case Insensitive to Case Sensitive. This of course is an illegal entry in the Data Migrator Filter window. Has anyone changed Collation in Data Migrator when dealing with SQL Server? thnx
...
Posts: 32 | Location: All over US | Registered: March 12, 2008