Frequently Asked Questions | Teradata Query Service - Query Service FAQ - Teradata Query Service

Teradata® Query Service Installation, Configuration, and Usage Guide for Customers - 4.01.03.01, 4.01.07.00

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Teradata Query Service
Release Number
4.01.03.01, 4.01.07.00
Published
September 2023
Language
English (United States)
Last Update
2024-02-16
dita:mapPath
qla1666844235399.ditamap
dita:ditavalPath
ft:empty
dita:id
enn1467244092237
Product Category
Analytical Ecosystem

General

  • Q: What are the benefits of Query Service API over standard Teradata drivers like JDBC, ODBC, Python, and so on?
    A: Functionally, there are no significant differences between Query Service API and standard Teradata drivers. If you are a developer, here are some reasons why you should use Query Service API:
    • Language-agnostic: If you use a programming language unsupported by Teradata native drivers.
    • Ease of use: You don’t have to manage client-side libraries in resource-constrained environments.
    • Streamlined third-party integration: REST is the standard interface for low-code or no-code applications.
  • Q: How does Query Service API perform better than other existing integrations?

    A: Different factors may affect the API performance, such as the design and use cases of the client-side application that consumes the API. As standard Teradata Drivers power Query Service API, there are no specific performance improvements under similar integration conditions.

  • Q: What are some common use cases for Query Service?
    A: You can use Query Service for:
    • Analytic workflows and custom applications that perform tactical queries.
    • Applications that require DML and DDL SQL statement interactions and want to interact using REST API.
    • Resource-constrained environments where you cannot install client libraries.
    • Direct low-code or no-code platform integrations that connect through Open APIs such as Power Apps, Salesforce Lightning, and so on.
    • Integrate in-database model scoring with tactical applications, for example, real-time credit risk scoring and customer recommendation.

    If you are interested in learning how Query Service can help solve your business challenges, contact Teradata.

Installation and Setup

  • Q: What is the recommended minimum hardware for deploying Query Service on my infrastructure?

    A: If you are a VantageCloud Enterprise user, the minimum requirements do not apply because Query Service runs as a core service on the platform.

Migration to VantageCloud Enterprise

  • Q: How do I configure and start Query Service on VantageCloud Enterprise?

    A: Query Service is available and provisioned by default for VantageCloud Enterprise. No special configurations are required besides standard network connectivity configurations.

  • Q: How do I configure and start Query Service on VantageCloud Enterprise?

    A: Query Service is available and provisioned by default for VantageCloud Enterprise. No special configurations are required besides standard network connectivity configurations.

  • Q: How do I configure and start Query Service on VantageCloud Enterprise?

    A: Query Service is available and provisioned by default for VantageCloud Enterprise. No special configurations are required besides standard network connectivity configurations.

  • Q: How do I configure and start Query Service on VantageCloud Enterprise?

    A: Query Service is pre-configured and automatically provisioned on VantageCloud Enterprise. No additional setup is needed beyond the standard network configuration.

  • Q: I am currently using Query Service on Teradata VantageCore (on-prem) and will be migrating to VantageCloud Enterprise soon. Will my applications work seamlessly?

    A: Yes, Teradata VantageCore to VantageCloud Enterprise transition is seamless, as the Query Service API endpoints remain the same. However, you may need to modify the Query Service variables, such as the hostname ( QS_HOSTNAME) and authentication method.

Data Limitation

  • Q: Are there any data type limitations when using Query Service API?

    A: There are no data type limitations for Query Service API.

  • Q: Are there use cases where Query Service should not be used, given limitations?

    A: Teradata does not recommend using Query Service beyond transactional cases, such as bulk data loading or real-time streaming.

Data Request

  • Q: Does Query Service API have a maximum result set size?

    A: Query Service limits the result set to 10,000 rows by default. This limit is set by the rowLimit field in the API request body. You can override this value based on your business requirements.

  • Q: Does Query Service API have a maximum response size?

    A: No, currently, Query Service API does not have a maximum response size. However, you can limit the result set size using the rowLimit field in the API request body. The result set size is set to 10,000 rows by default and can be modified for each API request.

  • Q: For Query Service API ASYNC requests, how long is the response stored on the server?

    A: You can set the retentionSpool parameter to define the number of hours Query Service stores the asynchronous query response before deleting them.

    The minimum setting is 1 hour, and the default value is 24 hours. Query Service deletes all spool files that exceed the maximum retention time.

    If you are a VantageCloud Enterprise user, you cannot modify the default value.

  • Q: Does Query Service API support multiple SQL statements for the same session?

    A: Yes, Query Service API supports multiple SQL statements. For information on how to manage multiple SQL statements, see Configuring Concurrent Queries.

  • Q: Does Query Service API have any SQL statement limitations?

    A: There are no significant SQL statement limitations as Query Service is built on top of standard Teradata drivers.