• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 424
  • Last Modified:

Time zones handle in SQL Server 2012


Currently we’re using Merge Replication (Push and Pull) for our application.
We’ve our Publisher DB located at EST time zone. And all 53 subscribers were located in different time zones.
14 subscribers were located at EST time zone
23 subscribers were located at PST time zone
12 subscribers were located at MST time zone
4 subscribers were located at CST time zone

Now we’re planning to use centralized DB with “Always ON” feature in SQL Server 2012 for our application.
But we’re having problem because of different time zones. We would like to do minimal changes to our application to handle time zone.

My Plan: To update all the related tables with proper Date and time using Stored procedure and function as we’ve used Now statement at many places.
I don’t think Triggers is the best solution as I’ll need to update minimum 25 tables at a time. And 100 users will do the same transactions at the same time.

Can you please provide suitable solution for these scenario?
1 Solution
Shaun KlineLead Software EngineerCommented:
Depending how minimal of a change you are looking for, you might want to consider the datetimeoffet data type: http://msdn.microsoft.com/en-us/library/bb630289.aspx.

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now