Focal Point Banner


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.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     Any degradation due to RDBMS ACTUAL formats too big?

Read-Only Read-Only Topic
Go
Search
Notify
Tools
Any degradation due to RDBMS ACTUAL formats too big?
 Login/Join
 
Virtuoso
posted
I am using WF to report from Oracle RDBMS. The ACTUAL formats for one particular field was generated as A70V by the CREATE SYNONYM. However, the longest value in the entire database is 6 chars for this field. Is there an advantage to shrinking the MFD to say A6V as opposed to leaving it as A70V but having the USAGE format as A6V? How about using A6 (without the V) for both USAGE and ACTUAL formats? Any performance gains/losses?


Thanks!

Mickey

FOCUS/WebFOCUS 1990 - 2011
 
Posts: 995 | Location: Gaithersburg, MD, USA | Registered: May 07, 2003Report This Post
Virtuoso
posted Hide Post
I'm not sure about the actual, but I changed the usage many times to the length I was sure that would be convenient and also that "V" is many times removed.

No problem until now.




Frank

prod: WF 7.6.10 platform Windows,
databases: msSQL2000, msSQL2005, RMS, Oracle, Sybase,IE7
test: WF 7.6.10 on the same platform and databases,IE7

 
Posts: 2387 | Location: Amsterdam, the Netherlands | Registered: December 03, 2006Report This Post
Master
posted Hide Post
Here's a bit of code you can adapt to give you actual stats on RDBMSes

I tend to set actuals to the max length gened by this script (will error if actual is less than length of data item in a particular record) with usage being chosen on the basis of the stats (does not have to be the same as actual).

-*=================================================================================================================================================
-* MAXIMUM FIELD LENGTHS
-*=================================================================================================================================================

-IF &ACTION NE 'M' THEN GOTO NO_MAXLEN ;
-MAXLEN
-SET &ECHO=ON ;

TABLE FILE SYSTABLE
PRINT DBMS_CREATOR REALNAME
IF NAME EQ '&LFILENAME'
ON TABLE SAVE AS SAVETXS
END
-RUN
-READ SAVETXS &DBMS_CREATOR.A8. &REALNAME.A64.
-SET &DBMS_CREATOR = TRUNCATE(&DBMS_CREATOR) ;
-SET &REALNAME = TRUNCATE(&REALNAME) ;

TABLE FILE SYSCOLUM
PRINT ALIAS LENGTH
IF TBNAME EQ '&LFILENAME'
IF NAME NE ' '
IF ACTUAL LIKE 'A%'
ON TABLE SAVE AS SAVEIJK
END
-RUN

-REPEAT LOOP2IJK FOR &CTR FROM 1 TO 4 ;

-SET &FN = IF &CTR EQ 1 THEN 'MAX' ELSE IF &CTR EQ 2 THEN 'AVG' ELSE IF &CTR EQ 3 THEN 'COUNT' ELSE 'COUNT DISTINCT' ;

SQL &ADAPTER PREPARE SQLOUT FOR

-READ SAVEIJK &ALIAS.A66. &LENGTH.A4.
-IF &IORETURN NE 0 THEN GOTO LOOP1IJK ;
-SET &ALIAS = TRUNCATE(&ALIAS) ;
-SET &ALIASLENGTH = &ALIAS || LJUST(&LENGTH.LENGTH,&LENGTH,&LENGTH);

-SET &FUNCTION = IF &ADAPTER EQ 'SQLMSS' THEN 'LEN' ELSE 'LENGTH' ;

-IF &CTR EQ 4 THEN GOTO YES_DIST1 ;
SELECT &FN(&FUNCTION(&ALIAS)) AS &ALIASLENGTH
-YES_DIST1
-IF &CTR NE 4 THEN GOTO NO_DIST1 ;
SELECT COUNT( DISTINCT &ALIAS ) AS &ALIASLENGTH
-NO_DIST1

-READ SAVEIJK &ALIAS.A66. &LENGTH.A4.
-REPEAT LOOP1IJK WHILE &IORETURN EQ 0;
-SET &ALIAS = TRUNCATE(&ALIAS) ;
-SET &ALIASLENGTH = &ALIAS || LJUST(&LENGTH.LENGTH,&LENGTH,&LENGTH);


-IF &CTR EQ 4 THEN GOTO YES_DIST2 ;
 , &FN(&FUNCTION(&ALIAS)) AS &ALIASLENGTH
-YES_DIST2
-IF &CTR NE 4 THEN GOTO NO_DIST2 ;
 , COUNT( DISTINCT &ALIAS ) AS &ALIASLENGTH
-NO_DIST2

-READ SAVEIJK &ALIAS.A66. &LENGTH.A4.
-LOOP1IJK

-CLOSE SAVEIJK
-*FROM &DBMS_CREATOR|.&LFILENAME ;
FROM &REALNAME ;
END
-RUN
TABLE FILE SQLOUT
HEADING
" &FILENAME Fieldsize &FN "
PRINT *
END
-RUN

-LOOP2IJK

-NO_MAXLEN





Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2
Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
 
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     Any degradation due to RDBMS ACTUAL formats too big?

Copyright © 1996-2020 Information Builders