Forum Widgets
Latest Discussions
Message=Keyword or statement option 'tzoffset' is not supported in this version of SQL Server.
Hi, We use Dynamics 365 (D365) as our transactional system. For reporting, we were using Data Export Services (DES) that pushed D365 data to Azure SQL Server where I created SQL Views on top of the D365 data. Power BI reporting then extracted from those SQL Views. All was working fine until Microsoft (MS) decided to deprecate DES and suggested Synapse as the substitute. We followed MS's suggestion. Whilst migrating all over what I found is a lot of standard Azure SQL functions weren't compatible with Synapse and so I had to handle those incompatibilities. In the end, all was working and has been for the past eighteen months since that migration exercise. Overnight, the scheduled Power BI (PBI) reports are failing their data refreshes due to the below error: When I open the same report from PBI Desktop and open the Advanced Editor to have Power Query re-evaluate against the source SQL Views, I get this error message: Both messages are referring to the 'tzoffset' word/code that is used in the SQL Views to handle the UTC/local timezone datestamps. The line of code in the SQL View is: The above line of code is something Synapse did allow eighteen months ago. Although the error messages refer to SQL, the SQL Views query Synapse data and so the technology not accepting the 'tzoffset' code will be Synapse. To test this, I queried Synapse directly from within Synapse inteface (ignoring any reference to our Dynamics 365 data or our use of SQL Views) and I received the below error. You can see I was referencing the Master db and simply calling the system time. I haven't changed anything in my Power BI reporting, SQL Views, or Synapse. No code changes, no software updates in the last week or so. I do not know what has caused the 'tzoffset' to no longer be supported. I have a strong suspicion that if I were to remove any reference to 'tzoffset' in my SQL Views then there could well be another error that arises. It's often the cause that you have to resolve the showing error only for the next error in line to show. Point being, will there be further code snippets that Synapse has overnight decided not to allow. Can anyone advise what could be causing this as in why all of a sudden (with no changes to anything) has Synpase started to not allow 'tzoffset'? Thanks.
Reader only access unable to login synapse workspace or SSMS into the database
Hello, Just wondering My colleagues were placed under the default role provided by Microsoft as a 'reader' under the synapse workspace. But we do not understand why they are unable to signin the workspace or SSMS of synapse. Would you be able to rectify it for us please?
