Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Integration
  • All Products

Table of Contents

Search

  1. Preface
  2. Components
  3. API collections
  4. Business services
  5. File listeners
  6. Fixed-width file formats
  7. Hierarchical mappers
  8. Hierarchical schemas
  9. Industry data service customizer
  10. Intelligent structure models
  11. Refining intelligent structure models
  12. Mapplets
  13. Saved queries
  14. Shared sequences
  15. User-defined functions

Components

Components

Back Next

Saved query syntax

Saved query syntax

When you create a saved query, enter an SQL statement that is valid for the database that you want to run the query against.
You can use different SQL statements based on where you use the saved query:
Synchronization
 task
When you create a saved query to use as the source in a synchronization task, the SQL statement must be a SELECT statement.
Data Integration
 uses the SQL statement to retrieve source column information. You can edit the data type, precision, or scale of each column before you save the saved query.
For example, you might create a saved query based on a TRANSACTIONS table that includes transactions from 2016 with the following SQL statement: 
SELECT TRANSACTION_ID, TRANSACTION_TOTAL, TRANSACTION_TIMESTAMP from dbo.TRANSACTIONS WHERE TRANSACTION_TIMESTAMP>’0:0:0:0 01/01/2016’
Data Integration
 ensures that saved query column names are unique. If an SQL statement returns a duplicate column name,
Data Integration
 adds a number to the duplicate column name as follows:
<column_name><number>
SQL transformation
When you create a saved query to use in an SQL transformation, you can use one or more of the following SQL statements in the query:

    ALTER

    CALL

    COMMENT

    COMMIT

    CREATE

    DELETE

    DROP

    EXPLAIN PLAN

    GRANT

    INSERT

    LOCK TABLE

    MERGE

    RENAME

    REVOKE

    ROLLBACK

    SELECT

    TRUNCATE

    UPDATE

Use the following guidelines when you create the query:
  • You can use aggregate functions such as COUNT with Salesforce connections only.
  • Do not use conversion functions, such as TO_CHAR or TO_DATE.
  • Do not use an asterisk (*) to select all columns of a table. List the columns that you want to select.
  • Do not use SQL transformation parameter binding or string substitution notation such as ?input_field? or ~input_field~ in the query. Saved queries have no information about SQL transformation input fields.
Test the SQL statement you want to use on the source database before you create a saved query.
Data Integration
 does not display specific error messages for invalid SQL statements.
0 COMMENTS
We’d like to hear from you!