Empty response on SQL-Server queries containing DATETIME

Metabase version: 0.33.4

Works for me, I’m also using 0.33.4:

Anything non-standard about your MS SQL install?
What happens if you click the play button?

MS-SQL looks fine, queries run easily on SSMS.
I’ve also tried to use another instance of Metabase on my PC and that worked fine.

About clicking the play button, there is no error or warning, the only thing I get is an empty response with status code of 200.
Server log:

2019-11-04T11:10:20+03:30 DEBUG metabase.middleware.log POST /api/dataset 200 [ASYNC: completed] 298.9 ms (9 DB calls) Jetty threads: 2/50 (5 idle, 0 queued) (147 total active threads) Queries in flight: 0

What happens if you start a new question, then enter the query again? I don’t know how you’ve got the play button displaying if the query hasn’t just been modified.

Any query containing a DATETIME column results in empty response. even when I use query builder.
query on entire table for example.

The play button is not the issue, the problem is that “The API endpoint is not working properly”.
I’ve tested the API with Postman and the result was the same.

Are you sending Metabase a datetime(6) value? It doesn’t render these property and is a known issue; I will try to dig up the references. Try casting to string / datetime(3) and see how you go?

@balibaba I think you’re seeing this issue, which is probably what @chucklessmith was thinking about:
https://github.com/metabase/metabase/issues/10285
But all the reports has been about MySQL, so I’m unsure if this is the exact same problem with SQL Server.

please consider that I can’t change the column data type in the database.
and my problem is not getting null value on the rows, the problem is that the whole response fails with no errors.
@chucklessmith casting to string works fine(as you can see in the first screenshot)

@balibaba
Which version of SQL Server?
And to reproduce this issue, you simply make a query like select getdate() ?
When you say that you tried from another Metabase instance and it worked - what’s the difference between the two instances?

Which version of SQL Server?

14.0.1000.169

And to reproduce this issue, you simply make a query like select getdate() ?

Yes

When you say that you tried from another Metabase instance and it worked - what’s the difference between the two instances?

The instance with problem: hosted on Kubernetes, with a MariaDB database
“another Metabase instance” : hosted on my own pc, os:windows 10, H2 database

@balibaba Okay, that seems like an interesting issue, but difficult to debug.
At least now, it seems like it’s not an issue with the SQL Server, but maybe the MariaDB.

Are there any special connection string parameters for the SQL Server (Admin > Database)?

Can you supply Diagnostic Info from both instances (Admin > Troubleshooting)?

Which version of MariaDB? Do you see any activity in the log of MariaDB, when running the failing query?