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.
Right now we have our reports grab data from MSSQL. Some reports call Store Procedure, (Store Proc has all the logic for the results), to get the results to display, and other reports call DB Tables to get data and does calculation for the report in .FEX
How would the reports be affected from switching our DB from MSSQL to ORACLE? Is there anything that we have to change or re-write in our Reports that call Store Proc, or reports that have all logic in itself?
Thank you for your answers in advance.This message has been edited. Last edited by: Alex Moon,
Alex - It really depends on how your reports are written. Are you using metadata or SQL pass thru? Is your SQL specific to MSSQL? If using metadata, Webfocus might interpret the tables differently when creating synonyms.