C#：当插入到 DateTimeOffset SQL 服务器列时，如何停止将时区偏移添加到 System.DateTime

Question

I have some C# code that copies rows from one database and inserts them into another. It does this using a DataTable and SqlBulkCopy .

When imported into my C# application, the timestamp columns have the data type System.DateTime inside the DataTable that is inserted into SQL Server. Once SqlBulkCopy.WriteToServer() has executed, timestamp values inside the destination tables have the type datetimeoffset(6) and have a timezone offset added to them (... +01:00).

How do I stop this happening? It hasn't always happened, only started happening recently.

UPDATE:

The timezone expected is UTC, always, for my purposes. However, I am forced to store this in a datetimeoffset column for business reasons. So I'm expecting +00:00

DataTable data = importer.GetDataTable();

using (SqlBulkCopy copy = new SqlBulkCopy(conn)){
   copy.WriteToServer(data);
}

Answer 1

If you have a DateTime and try to write it to a DateTimeOffset C# has to figure out what timezone to use. There are explicit conversion functions that allow you to specify but if you don't it will assume the DateTime is in the local timezone (as the majority of the time they are).

https://docs.microsoft.com/en-us/dotnet/standard/datetime/converting-between-datetime-and-offset provides several examples on how to convert between the two. Note that SpecifyKind doesn't require having a DateTimeOffset type.

Answer 2

Using DateTime.SpecifyKind() on timestamp columns before inserting them into Sql Server didn't work for me.

I solved this by converting (casting) the System.DateTime columns to DateTimeOffset with an explicit offset of new TimeSpan(0, 0, 0) . This removed the need for C# to implicitly handle the conversion from DateTime to DbType.DateTimeOffset which was adding an undesired offset.

EDIT

Reading the comments, @JohnSkeet essentially recommended this but I hadn't read everyone's comments.