> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-data-stack-v10/functions/logical/isvalidsqldate-date.md).

# IsValidSqlDate (Date)

| **Name**    | ***IsValidSQLDate***                                                                                                   |
| ----------- | ---------------------------------------------------------------------------------------------------------------------- |
| Syntax      | IsValidSqlDate (Date date)                                                                                             |
| Purpose     | To check if a date time value is a valid SQL Date time value.                                                          |
| Description | Returns true if the specified date time value is within the range of a valid SQL Server date. Otherwise returns false. |
| Return Type | Boolean                                                                                                                |
| Parameters  | date \[System.DateTime] – DateTime value to be checked                                                                 |

![](https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FyqfyKAJa2AJWw0X3uRzB%2F0.png?alt=media)

### **Example**

In this example, we will pass various SQL DateTime values to the function transformation object using a *Variables* objec&#x74;*,* along with the *Normalize* object so that different values can be passed to the function transformation object at once.

Where,

*date1* = 1 January, 2003

*date2* = January, 2003

*date3* = 1/2/1991

*date4* = 1991/2/4

*date5* = 0000/00/00

{% hint style="info" %}
**Note:** Valid SQL server DateTime range is “January 1, 1753” – “December 31, 9999”
{% endhint %}

![](https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2FPEXtdW8btb1DiT7qXZgK%2F1.png?alt=media)

In the output window, you can see that the Boolean value, True, has been returned for values that are present in the valid SQL server DateTime range, and the value, False, has been returned otherwise.

![](https://3083465318-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsR50Wa7EwZGlmPSAMkkf%2Fuploads%2F40CU1isgASg5McNH0yGR%2F2.png?alt=media)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.astera.com/astera-data-stack-v10/functions/logical/isvalidsqldate-date.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
