TSQL : Unix timestamp into Local time in sql server

DECLARE @epoch bigint
SET
@epoch = 1399518300002

select DATEADD(minute, DATEDIFF(minute, getutcdate(), getdate()), DATEADD(s, @epoch/1000, '19700101 00:00:00:000'))

Comments

Post a Comment

Popular posts from this blog

SQL Server MDS : How to Know Actual MDS Table name for Model Entity and Column name for the Attribute

How to Know Actual MDS Table name for Model Entity and Column name for the Attribute . here is the Script  USE MDS ------------------------------------------------------------ -- TODO: Define Model name, Entity name, and Attribute Name        DECLARE @Model NVARCHAR ( 50 )        = '<<GiveModelName>>' ;        DECLARE @Entity_Name NVARCHAR ( 50 ) = '<<GiveEntityName>>' ;        DECLARE @Attribute_Name NVARCHAR ( 50 )= '<<GiveAttributeName>>' ; ------------------------------------------------------------ -- Set @Table name        DECLARE @Table NVARCHAR ( 128 );              SELECT @Table = EntityTable FROM mdm . viw_SYSTEM_SCHEMA_ENTITY WHERE Model_Name = @Model AND name = @Entity_Name ; --...
Read more

SSIS : Hresult: 0x80004005 Description: "Invalid character value for cast specification".

Image
1.       Error msg: [OLE DB Destination [138]] Error: SSIS Error Code DTS_E_OLEDBERROR.   An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available.   Source: "Microsoft SQL Server Native Client 10.0"   Hresult: 0x80004005   Description: "Invalid character value for cast specification". [OLE DB Destination [138]] Error: There was an error with input column "finDate" (2050) on input "OLE DB Destination Input" (151). The column status returned was: "The value could not be converted because of a potential loss of data.". [OLE DB Destination [138]] Error: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR.   The "input "OLE DB Destination Input" (151)" failed because error code 0xC0209077 occurred, and the error row disposition on "input "OLE DB Destination Input" (151)" specifies failure on error. An error occurred on the specified object of the specified compone...
Read more

SSRS : [Teradata Database] 3939 There is a mismatch between the number of parameters specified and the number of parameters required.

Error : [Teradata Database] 3939   There is a mismatch between the number of parameters specified and the number of parameters required. When we get this Error : when we are creating SSRS reports on Teradata database and in which when we are using parameters in the dataset in wrong style\format. Just for Info :  to connect Terdata we need to have  .Net Data provider for Terdata  when we installed this on our machine  Then we are able to see Teradata data source type in SSRS. How to Solve this issue :  This error will come if we are not using correct syntax to create parameterized data set .  The correct way is we need to ?  for parameter The report parameters can be named or unnamed. Teradata only supports unnamed parameters. An unnamed parameter is denoted by a ‘?’, and is merely a placeholder for data that is going to be entered at report processing time. For example, the following is a dataset with a single-value ...
Read more