I understand that, but converting to or from a Unix timestamp doesn't need to know anything about UTC.  The conversion is strictly based on the number of seconds or milliseconds...

You seem to continue mixing/matching different data types and expecting correct values.  Is the column t_stamp the old Unix timestamp based only on seconds - or is it the new...

Not surprising - what dates/times did you see prior to 12/21?  Based on your code - I suspect you are going to see dates and times that are not the...

I would recommend reviewing this article: https://www.sqlservercentral.com/articles/convert-unix-timestamps-to-date-times-in-sql-server-part1

It looks like your calculation for the UNIX timestamp is incorrect.  From that article (@JeffModen):

--===== Convert a given Date/Time to the...

I would modify the query so that I wasn't converting the t_stamp value to a date in the where clause.  I might also move the conversion in the openquery -...

WHERE cast(datetime_column AS time(0)) <= '06:00:00'

If you don't want to include 06:00:00 - then rewrite it as:

WHERE cast(datetime_column AS time(0)) < '06:00:00'

Take a look at the Powershell tools for SSRS - you may be able to use those to update the schedule end dates.

For a simple query like this - I would also use NOT IN, but I would also use the code instead of the name.  For more complex queries - it...

Select the project properties - change the target server version to the instance of SQL Server you are going to deploy this package.

Yes - you need some type of witness for the cluster.  Cluster quorum must be more than 50% votes - and if you only have 2 nodes, as soon as...

That is good to know - thank you for the update.

I think you misunderstood what I was saying though - the process is: Right-Click on the dtsx package and Open...

Sorry, what I mean is that when they right click the "The Execute Package Utility" option is not available- it doesn't show up anymore. The only thing that shows...

When they right-click, open with - are they navigating to that file and selecting it?  Not sure what you mean when you say it isn't available anymore.  You verified it...

Is there an error?  What happens when they try to run the package?  Are they actually running a package - or that is ISPAC file they are trying to run?

Also - the default settings for autogrowth are horribly wrong and problematic, especially for the transaction log.  That setting of 10% means the next growth is going to be 18890MB...