Now, you can save your searches to easily repeat search requests.
Saving a search is as easy as 1-2-3:
1. Perform a search. The Search Results page opens. 2. Optionally, choose filters or update your search term. 3. Click Save Search.
You can access saved searches from a list next to the Search field that appears on every page. Saved searches store the search term and any search filters that you apply.
Rules and Guidelines for Functions in Pushdown Optimization
Rules and Guidelines for Functions in Pushdown Optimization
Use the following rules and guidelines when pushing functions to a database:
Relational Databases
If you use ADD_TO_DATE in transformation logic to change days, hours, minutes, or seconds, you cannot push the function to a Teradata database.
When you push LAST_DAY() to Oracle, Oracle returns the date up to the second. If the input date contains subseconds, Oracle trims the date to the second.
When you push LTRIM, RTRIM, or SOUNDEX to a database, the database treats the argument (' ') as NULL, but the PowerCenter Integration Service treats the argument (' ') as spaces.
An IBM DB2 database and the PowerCenter Integration Service produce different results for STDDEV and VARIANCE. IBM DB2 uses a different algorithm than other databases to calculate STDDEV and VARIANCE.
When you push SYSDATE or SYSTIMESTAMP to the database, the database server returns the timestamp in the time zone of the database server, not the PowerCenter Integration Service.
If you push SYSTIMESTAMP to an IBM DB2 or a Sybase database, and you specify the format for SYSTIMESTAMP, the database ignores the format and returns the complete time stamp.
PowerExchange for Amazon Redshift
To push TRUNC(DATE) to Amazon Redshift, you must define the date and format arguments. Otherwise, the PowerCenter Integration Service does not push the function to Amazon Redshift.
The aggregator functions for Amazon Redshift accept only one argument, a field set for the aggregator function. The filter condition argument is not honored. In addition, make sure that all ports mapped to the output are listed in the GROUP BY clause.
For Amazon Redshift, when you define only a string argument for TO_DATE() and TO_CHAR(), the PowerCenter Integration Service considers the default date format present in the session property. The default date format in the session property is: MM/DD/YYYY HH24:MI:SS.US
Do not specify a format for SYSTIMESTAMP() to push the SYSTIMESTAMP to Amazon Redshift. The Amazon Redshift database returns the complete time stamp.
To push INSTR() to Amazon Redshift, you must only define string, search_value, and start arguments. Amazon Redshift does not support occurrence and comparison_type arguments.
The flag argument is ignored when you push TO_BIGINT and TO_INTEGER to Amazon Redshift.
The CaseFlag argument is ignored when you push IN() to Amazon Redshift.
If you use the NS format as part of the ADD_TO_DATE() function, the PowerCenter Integration Service does not push the function to Amazon Redshift.
If you use any of the following formats as part of the TO_CHAR() and TO_DATE() functions, the PowerCenter Integration Service does not push the function to Amazon Redshift:
NS
SSSS
SSSSS
RR
To push TRUNC(DATE) and DATE_DIFF() to Amazon Redshift, you must use the following formats:
D
HH24
MI
MM
MS
SS
US
YYYY
To push GET_DATE_PART() to Amazon Redshift, you must use the following formats:
D
DDD
HH24
MI
MM
MS
SS
US
YYYY
PowerExchange for Netezza
You can push SYSTIMESTAMP(‘SS’) to a Netezza database, but not SYSTIMESTAMP(‘MS’) or SYSTIMESTAMP(‘US’).
When you push TO_CHAR(DATE) or TO_DATE() to Netezza, dates with subsecond precision must be in the YYYY-MM-DD HH24:MI:SS.US format. If the format is different, the PowerCenter Integration Service does not push the function to Netezza.
PowerExchange for Vertica
If you use any of the following formats as part of the DATE_DIFF() function, the PowerCenter Integration Service does not push the function to Vertica:
YYY
MON
MONTH
HH12
HH24
When you push the DATE_DIFF function to Vertica, Vertica rounds the date difference value to the nearest integer. However, the PowerCenter Integration Service returns a float value. For example, if the first date is 2000-08-15 and the second date is 1997-08-16, Vertica rounds the date difference value to 3, but the PowerCenter Integration Service returns 2.99731182795699. If you want the date difference to be treated as a float value in the Vertica database, you can disable pushdown optimization.
When you specify the format as Y and push the DATE_DIFF function to Vertica, Vertica calculates the difference in the dates in terms of number of days. However, the PowerCenter Integration Service calculates the difference in terms of number of years. If you want the difference value to be treated in terms of number of years, you can disable pushdown optimization.
PowerExchange for Greenplum
To push TRUNC(DATE) to Greenplum, you must use the following formats: