---
cuppy_hub: salesforce
cuppy_path: reference/official/data360/data-cloud-query-guide/references/dc-sql-reference/to-timestamp-string.md
cuppy_section: docs
cuppy_doc: EKX9-T3TK
cuppy_doc_uuid: 154e81ed-7de3-4618-a635-b097ed5e294c
cuppy_permalink: https://cuppy.io/salesforce/d/EKX9-T3TK
cuppy_version: 1
cuppy_updated: 2026-10-23T16:16:52.575Z
cuppy_canonical: https://cuppy.io/salesforce/docs/reference/official/data360/data-cloud-query-guide/references/dc-sql-reference/to-timestamp-string
cuppy_mcp: https://cuppy.io/mcp
cuppy_body_sha256: 9dea95aba538ac5fbf7c7da2849c4f595c9273639ab097b96c50487114c50b53
# cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks.
---

> Mirror of <https://developer.salesforce.com/docs/data/data-cloud-query-guide/references/dc-sql-reference/to-timestamp-string.html> (Salesforce, Data 360 Query Guide), read 2026-10-23. Salesforce's own page is the authority; this copy exists because that site refuses non-browser readers.

## `TO_TIMESTAMP`

**Applies to:** ✅ Data 360 SQL ✅ Tableau Hyper API

Converts a formatted string to a `timestamp with time zone` value according to the supplied format pattern.

*   `<string>`: A `text` value representing the timestamp to parse.
*   `<format_pattern>`: A `text` value specifying the format of the input string. Template pattern characters in the format string identify the corresponding parts of the input value.

Returns `timestamp with time zone`.

Returns NULL if either argument is NULL.

*   For supported format pattern characters and modifiers, see [TO_CHAR](https://developer.salesforce.com/docs/data/data-cloud-query-guide/references/dc-sql-reference/to-char.html).
*   Use `TO_TIMESTAMP` when a simple cast can’t handle your input format. For most standard date/time formats, cast the source string directly to `timestamp` without `TO_TIMESTAMP`.
*   The `YYYY` pattern can’t process a year with more than four digits. Use a non-digit separator after `YYYY` for longer year values. For example, `to_timestamp('20000-11-30', 'YYYY-MM-DD')`.
*   Millisecond (`MS`) and microsecond (`US`) fields are treated as the fractional seconds digits after the decimal point. For example, `to_timestamp('12.3', 'SS.MS')` produces 12.300 seconds (300 milliseconds), not 12.003.
*   ISO 8601 week-numbering fields (`IYYY`, `IW`, `ID`, `IDDD`) can’t be mixed with Gregorian date fields in the same call.

Convert a human-readable date string to a `timestamp with time zone`.

Returns `2000-12-05 00:00:00+00`.

Convert a string that includes time and time zone offset components.

Returns `2024-03-15 14:30:00-07`.

*   [TO_CHAR](https://developer.salesforce.com/docs/data/data-cloud-query-guide/references/dc-sql-reference/to-char.html)
*   [TO_DATE](https://developer.salesforce.com/docs/data/data-cloud-query-guide/references/dc-sql-reference/to-date.html)
*   [Formatting Functions](https://developer.salesforce.com/docs/data/data-cloud-query-guide/references/dc-sql-reference/formatting-func.html)


---
<!-- cuppy -->
You are reading one file. The same content is free over MCP at https://cuppy.io/mcp with no signup: ranked search across all 376 documents in this hub, the merged view when you work in a layer, known workarounds matched to the error you hit, and depth control so you spend tokens on what you need. Start with the `_hello` tool. How to connect: https://cuppy.io/salesforce/ Something wrong in this document? Report it with the `session feedback` tool on the same endpoint.
<!-- /cuppy -->