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.
I have an ACX File for an MS-SQL table: SEGNAME=BOOKS, CARDINALITY=564, TABLENAME=dbo.Books, CONNECTION=AudioBooks, KEYS=1, $ FIELD=BOOKID, AUTOINCREMENT=YES, START=1000, INCREMENT=1, $ The only definition I have found indicates it is to indicate 1:1, 1:M and M:M relationships. What is a 564 ?This message has been edited. Last edited by: <Kathryn Henning>,
WebFOCUS 8.0.2, FOCUS since 1977 - John@Aviter.com PDF , Excel, FOCUS, Author of the Keysheets and Dates book. www.Aviter.com
I suppose the syntax is there to carry hints that may help the SQL-generator optimize the generated SQL (although I would think the RDBMS is much better at that game).
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
If memory serves me correctly, I believe it is the number of rows in the table. Depending on the adapter, the optimizer can use that value to make decisions on how to join tables. I seem to remember it should only be used for pretty static tables as you wouldn't want that value in your ACX if the actual value varies -- that could cause some inaccurate decisions by the optimizer.
Originally posted by Emily Duensing: If memory serves me correctly, I believe it is the number of rows in the table. Depending on the adapter, the optimizer can use that value to make decisions on how to join tables.
I imagine it also gets used in cross-database joins to determine which table to fetch entirely and which to select only specific values from (based on the result set from the smaller table). For example, if you have a table A and a table B with cardinalities of a billion rows and just 10 respectively, then it's much more efficient to select the 10 rows from table B and apply an IN() clause to table A with those values than it would be to fetch the entirety of table A.
I don't know if WebFOCUS is smart enough to do that. I hope it is.
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :
Francis, This is a MS-SQL datsabase table. Autoincrement is the result of the MS-SQL IDENTITY function - which automatically increments the key field when adding new records.
WebFOCUS 8.0.2, FOCUS since 1977 - John@Aviter.com PDF , Excel, FOCUS, Author of the Keysheets and Dates book. www.Aviter.com