Open cesar-loadsmart opened 1 year ago
Hey folks!
This stackoverflow entry, makes me believe the real problem is not specifying the Database: https://stackoverflow.com/questions/29151478/how-does-a-table-not-being-in-information-schema-or-systables-happen
I believe that making the connection string work properly will fix my issue.
Hey!
I'm having the same problems connecting to the database server, the only difference is that I can't connect even without database on the connection string.
Might add that I'm using the latest version in a built docker image and the host I'm installing superset on doesn't have internet connection.
Are you using windows authentication?
Here I'm using database authentication,
I'm also waiting for my local machine to be whitelisted once again so that I can test a built docker image at the latest version connecting to the Database.
I believe that by using windows authentication, your connection string should look different, not sure though.
What I've seen was you only needed to mention the user like "Domain\User" so the string would be something like: "mssql+pymssql://Domain>\<user>:<password>@<host:
Any updates on this topic?
@cesar-loadsmart
I think the issue is when you are using:
mssql+pymssql://<user>:<password>@<host>/?charset=utf8
or
mssql+pymssql://<user>:<password>@<host>:<port>
it connects to the master database, not your actual database
which I tested by making it like this:
mssql+pymssql://<user>:<password>@<host>:<port>/master
it worked perfectly but when changing the DB to the required one I got the same error
Didn't work. I've tested with another environment and it worked, the only difference is that the user i am connecting. For the environment that is not working the user is from a domain controller and the other is a local windows user.
@kikolouro My user connects perfectly through DBeaver but not sqlalchemy URL. can you please explain to me the difference between the two users? and if possible how to create it. Aslo, are you connecting to the Azure SQL server or Azure Synapse Analytics?
@RobLucchi
So I have two scenarios:
Scenario A
machine A - has superset and other services, linux machine and superset running on docker machine B - has SQL Server in a domain.
When connection superset to the SQL Server using a Domain User gives me the error.
Scenario B machine A - has superset and other services, linux machine and superset running on docker machine B - has SQL Server and it is NOT in a domain
When connecting superset to the SQL using a local user (since it isn't in a domain) does not give me a error.
Might add that machine A from scenario A and B are in different networks and the Scenario A is from a Client so a I don't have permission to do some things like local users, SQL users etc and they wont provide me.
When selecting a database type I choose "Microsoft SQL Server".
well it worked with me after adding autocommit=true to the pyodbc driver URL
mssql+pyodbc://USER:PASSWORD@HOST:PORT/Database?driver=ODBC+Driver+17+for+SQL+Server&autocommit=true
Yep same issue. Synapse Serverless works great with no issues. The second you try and connect to a dedicated pool well then you can only connect to the master database as described above. Queries don't work for me because the dedicated pool doesn't support full path cross database queries.
Hello all,
Did any of you find a solution to this problem? I tried every solution in this thread but I still was not able to connect to it. If I specify the driver I get an error that the URL has an unexpected "driver".
Please let me know if you find any solution for this... Stuck in this problem for some time.
This issue seems to have gone stale... is anyone still facing this? We might need someone to recapitulate the issue as it pertains to currently supported versions (3.1/4.0). If it's a superset bug, we can leave it open. If it's a config issue, it should be a GitHub discussion instead (I can migrate it). If nobody's worried about it anymore, we can certainly close it. We also warmly welcome documentation contributions if anyone knows a solution and wants to help others in the future.
I've followed this doc to connect Superset with a Microsoft SQL Server Database, but using the recommended connection string
mssql+pymssql://<Username>:<Password>@<Host>:<Port-default:1433>/<Database Name>/?Encrypt=yes
did not work:Logs are also unclear:
So, I tested some different connections string, the following two worked:
mssql+pymssql://<user>:<password>@<host>/?charset=utf8
mssql+pymssql://<user>:<password>@<host>:<port>
However, when checking the Database schema on SQL Lab, it only shows the system tables:
It's not a permissions problem, because it works on Dbeaver! Queries also work, by specifying the complete path such as:
select * from db_name.dbo.table_name;
The only problem is the fact that it is only displaying system tables and views.
How to reproduce the bug
Expected results
Show all tables inside the database
Actual results
Only shows system tables, such as:
Environment
2.0.0
pymssql==2.2.7
3.8
node 16
Checklist
Make sure to follow these steps before submitting your issue - thank you!
Additional context
This is not a database we own, so some tests would require getting in contact with the external provider, something We wouldn't like to do at this moment.