Justin Dowdy

@juliomfreitas what error message did you get from the pipeline? i was able to run (idling) sqlservr on a VM with 256MB of RAM and 1.5GB of swapspace

@amcsi can you share the relevant portion of the log (with the error)?

@amcsi given that log it actually looks like there just isn't enough virtual memory to run your query. the docker image i wrote just bypasses a restrictive policy it doesn't...

@Kokotewa perhaps this will help? https://github.com/justin2004/mssql_server_tiny

for a repl candidate for the main branch... do we want a failure to happen at vd start up if all the dependencies are not installed? @ajkerrigan 's repl will...

ah, nice tip. thanks @bcogrel

@danielbakas in your properties file could you have limited it to that one schema using the jdbc url? e.g. instead of ``` jdbc.url = jdbc:postgresql://pg:5432/postgres ``` maybe as [this](https://stackoverflow.com/questions/4168689/is-it-possible-to-specify-the-schema-when-connecting-to-postgres-with-jdbc) indicates...

but the root of the problem... ``` Cannot find relation "SYSMAN"."SYS_IOT_OVER_92814" (available choices: [...]) ``` is that because the user can enumerate the relations (including that one) but the user...

i think one of these might have worked for me: ``` # jdbc.url = jdbc:postgresql://postgres:5432/adventureworks?options=-c%20search_path%3Dperson # jdbc.url = jdbc:postgresql://postgres:5432/adventureworks?options=-c%20search_path=person ``` does oracle have similar options?

>Have you considered allowing for schema filtering in Ontop? i also think that would be a useful feature. i have a list of features ideas that i've been meaning to...