User manual BUSINESS OBJECTS BUSINESSOBJECTS XI FOR WINDOWS AND UNIX DATA ACCESS GUIDE

[. . . ] Data Access Guide BusinessObjects 11 Windows and UNIX 1 Copyright Copyright © 2004 Business Objects. If you find any problems with this documentation, please report them to Business Objects in writing at documentation@businessobjects. com. Trademarks Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are trademarks or registered trademarks of Business Objects SA or its affiliated companies in the United States and other countries. All other names mentioned herein may be trademarks of their respective owners. Contains IBM Runtime Environment for AIX(R), Java(TM) 2 Technology Edition Runtime Modules (c) Copyright IBM Corporation 1999, 2000. [. . . ] This is the default behaviour. REPLACE_COMMA_BY_CONCAT REPLACE_COMMA_BY_SEPARATOR= Yes|No Values Default Description Yes|No Yes In previous versions of Designer, a comma could be used to separate multiple fields in an object Select statement. For universes that already use the comma in this way you can set REPLACE_COMMA_BY_SEPARATOR to No to keep this behavior. In the current version of Designer, this parameter is set to Yes by default, so that a expressions using a comma in this way are automatically changed to use concatenation syntax. Yes: Comma is replaced by the concatenation expression when multi field object is found. No: Keep the comma as it is. Data Access Guide 65 6 Setting universe dynamic SQL parameters Dynamic SQL parameters in a universe SHORTCUT_BEHAVIOR SHORTCUT_BEHAVIOUR = Global|Successive Values Default Description Global|Successive Successive Specifies how shortcut joins are applied. This parameter was formerly listed as GLOBAL_SHORTCUTS in the PRM files. The values have been changed to Global for Yes, and Successive for No. A shortcut join is applied only if it really bypasses one or more tables, and if it does not remove a table from the join path used by a following shortcut join. Note: If it generates a Cartesian product, no shortcut joins are applied. THOROUGH_PARSE THOROUGH_PARSE = Yes|No Values Default Description Yes|No No Specifies the methodology used for default Parsing in the Query panel and individual object parsing. Yes: PREPARE, DESCRIBE, and EXECUTE statements are used to parse SQL for objects. Prepare+DescribeCol+Execute No: PREPARE and DESCRIBE statements are used to parse SQL for objects. UNICODE_STRINGS UNICODE_STRINGS = Yes|No Values Yes|No 66 Data Access Guide Setting universe dynamic SQL parameters Dynamic SQL parameters in a universe 6 Default Description No Specifies whether the current universe can manipulate Unicode strings or not. If the database character set in the SBO file is set as Unicode, then it is necessary to modify the SQL generation to handle specific Unicode column types like NCHAR and NVARCHAR. Yes: Conditions based on strings are formatted in the SQL according to the value for a parameter UNICODE_PATTERN in the PRM file, for example for MS SQL Server (sqlsrv. prm): UNICODE_PATTERN=N$ The condition Customer_name='Arai ' becomes Customer_name=N'Arai'. No: All conditions based on strings are formatted in the standard SQL. For example the condition Customer_name='Arai ' remains Customer_name='Arai' Data Access Guide 67 6 Setting universe dynamic SQL parameters Dynamic SQL parameters in a universe 68 Data Access Guide Setting data access SQL parameters (PRM) chapter 7 Setting data access SQL parameters (PRM) Overview Overview This chapter provides an alphabetical reference for all SQL configuration parameters listed in <driver>. prm files. This reference describes the SQL parameters in the Configuration section. They are described here with information on how to use these parameters to optimize your data access. You can see the date operators, other operators, and functions available for your data access driver by opening the <driver>. prm file in an XML editor. Note: Certain parameters can be set in the Parameter page of the Universe Parameters dialog box in Designer (File > Parameters > Parameter). If you modify a parameter in Designer, the new value over rides any modification that you have made to the parameter value in the PRM file. The changes made in Designer apply only to the universe they are saved in, and the value in the PRM remains unchanged. See the Designer's Guide for more information. Data access driver SQL parameters Each data access driver is associated with a SQL parameters file (<driver>. prm). [. . . ] </Server> <Parameter Name="Max Pool Time">-1</Parameter> Description Determines the maximum connection idle lifetime in the connection pool regardless of the value defined in the connection. You can set Max Pool Time for two types of Connection Server deployments: Library: Value applies to nodes that have Connection Server installed with desktop or other server products. Server: Value applies to Connection Server stand alone server installations. For information on deploying Connection Server on a dedicated node see the Deployment guide. [. . . ]