In this Microsoft SQL Server 2025 series:
- Dec 01: Microsoft SQL Server 2025 – Introduction and installation
- Dec 02: Microsoft SQL Server 2025 – New T-SQL functions – native JSON data type and some functions
- Dec 03: Microsoft SQL Server 2025 – New T-SQL functions – JSON Index
- Dec 04: Microsoft SQL Server 2025 – New T-SQL functions – Product()
- Dec 05: Microsoft SQL Server 2025 – New T-SQL functions – BASE64_ENCODE() and BASE64_DECODE()
- Dec 06: Microsoft SQL Server 2025 – New T-SQL functions – REGEXP_LIKE()
- Dec 07: Microsoft SQL Server 2025 – New T-SQL functions – REGEXP_SUBSTR() and REGEXP_REPLACE()
- Dec 08: Microsoft SQL Server 2025 – New T-SQL functions – REGEXP_INSTR() and REGEXP_COUNT()
- Dec 09: Microsoft SQL Server 2025 – New T-SQL functions – REGEXP_MATCHES() and REGEXP_SPLIT_TO_TABLE()
- Dec 10: Microsoft SQL Server 2025 – External REST endpoint invocation
- Dec 11: Microsoft SQL Server 2025 – External REST endpoint invocation using LLM
- Dec 12: Microsoft SQL Server 2025 – New vector data type and Vector functions
- Dec 13: Microsoft SQL Server 2025 – Vector functions
- Dec 14: Microsoft SQL Server 2025 – Vector arrays or embeddings with function AI_GENERATE_EMBEDDINGS
- Dec 15: Microsoft SQL Server 2025 – T-SQL functions for AI External_Models, Chunks and Embeddings
- Dec 16: Microsoft SQL Server 2025 – Optional parameter plan optimization (OPPO)
- Dec 17: Microsoft SQL Server 2025 – Query hint ABORT_QUERY_EXECUTION
- Dec 18: Microsoft SQL Server 2025 – Optimized locking
This function returns the current database system date as a date value, without the database time and time zone offset. CURRENT_DATE derives this value from the underlying operating system on the Database Engine runs. This function is eqvivalent to CAST(GETDATE() AS DATE).
Let’s check the precisions to see, where we will lose the precision based on the system date/datetime functions.
SELECT CURRENT_DATE;
GO
-- precisions
SELECT
SYSDATETIME() AS Sys_datetime
,SYSDATETIMEOFFSET() AS sys_DatetimeOffset
,SYSUTCDATETIME() AS SysUTC_Datetime
,CURRENT_TIMESTAMP AS Curr_Timestamp
,GETDATE() AS Get_date
,GETUTCDATE() as Get_UTCDate
,CURRENT_DATE AS current_d
,CAST(GETDATE() AS DATE) as current_d_cast
Function current_date can be used also as default when creating a table:
DROP TABLE IF EXISTS dbo.TEST;
GO
CREATE TABLE dbo.test
(ID INT IDENTITY(1,1) NOT NULL
,tt CHAR(10) NULL
,dd DATE NOT NULL DEFAULT CURRENT_DATE
,ddtt SMALLDATETIME NOT NULL DEFAULT DATEADD(DAY,1,CURRENT_DATE)
)
INSERT INTO dbo.test (tt, dd)
SELECT 'aaa','2025-12-19' UNION ALL
SELECT 'bbb','2025-12-20 05:26:46.947' UNION ALL
SELECT 'ccc',GETDATE() UNION ALL
SELECT 'ddd',DATEADD(DAY, 8,CAST(GETDATE() AS DATE)) union all
select 'eee',CURRENT_TIMESTAMP
SELECT * FROM dbo.TEST
where current date and time (of making this test was: 19th December 2025, 06.20 AM CET).
Tomorrow we will look into the new CES feature in SQL Server 2025.
As always, the code is available at my Github: https://github.com/tomaztk/SQLServer2025
Happy coding!
TomazTsql 
[…] Dec 19: Microsoft SQL Server 2025 – New T-SQL functions – CURRENT_DATE […]
LikeLike
[…] Dec 19: Microsoft SQL Server 2025 – New T-SQL functions – CURRENT_DATE […]
LikeLike
[…] Dec 19: Microsoft SQL Server 2025 – New T-SQL functions – CURRENT_DATE […]
LikeLike
[…] Dec 19: Microsoft SQL Server 2025 – New T-SQL functions – CURRENT_DATE […]
LikeLike
[…] Dec 19: Microsoft SQL Server 2025 – New T-SQL functions – CURRENT_DATE […]
LikeLike