Hi @SwapnilSalunke-4731,
Welcome to Microsoft Q&A!
Unfortunately SQL Server doesn't yet support IANA time zone identifiers (like America/Chicago) directly.
For now, the best option is to convert from the IANA identifier to a corresponding Windows time zone identifier in your application layer, and store that in your SQL Server.
Since your version is SQL Server 2012 which "AT TIME ZONE " does not work, you could refer below which is an alternative approach.
-- all SQL Server versions
declare @utc_date datetime = getdate()
select @utc_date as utc_time_zone,
dateadd(hh, datediff(hh, getutcdate(), getdate()), @utc_date) as local_time_zone
In addition, it is also recommended to create and use a Calendar table.
Aaron Bertrand covers this exact scenario in depth here. You could refer it and find out more solutions.
Best regards,
Melissa
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.