Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pymssql showing in logs when pyodbc is specified #72

Open
wesseljt opened this issue Oct 20, 2023 · 5 comments
Open

pymssql showing in logs when pyodbc is specified #72

wesseljt opened this issue Oct 20, 2023 · 5 comments
Assignees

Comments

@wesseljt
Copy link

wesseljt commented Oct 20, 2023

config

  - name: tap-mssql--db
    inherit_from: tap-mssql
    variant: buzzcutnorman
    pip_url: git+https://github.com/BuzzCutNorman/tap-mssql.git
    config:
      dialect: mssql
      driver_type: pyodbc
      database: db1
      user: myuser
      port: 1433
      sqlalchemy_url_query:
        driver: ODBC Driver 17 for SQL Server
        trustServerCertificate: yes
        multiSubnetFailover: yes
      sqlalchemy_eng_params:
        fast_executemany: 'true'

inherit from

  - name: tap-mssql
    variant: buzzcutnorman
    pip_url: git+https://github.com/BuzzCutNorman/tap-mssql.git
    config:
      dialect: mssql
      driver_type: pyodbc
      port: 1433
      sqlalchemy_url_query:
        Driver: ODBC Driver 17 for SQL Server
      sqlalchemy_eng_params:
        fast_executemany: 'true'
@BuzzCutNorman BuzzCutNorman self-assigned this Oct 20, 2023
@wesseljt
Copy link
Author

wesseljt commented Oct 20, 2023

Error message

2023-10-20T17:57:03.736061Z [info     ] pymssql._pymssql.ProgrammingError: (207, b"Invalid column name 'dt_offset_col'.DB-Lib error message 20018, severity 16:\nGeneral SQL Server error: Check messages from the SQL Server\nDB-Lib error message 20018, severity 16:\nGeneral SQL Server error: Check messages from the SQL Server\nDB-Lib error message 20018, severity 16:\nGeneral SQL Server error: Check messages from the SQL Server\nDB-Lib error message 20018, severity 16:\nGeneral SQL Server error: Check messages from the SQL Server\nDB-Lib error message 20018, severity 16:\nGeneral SQL Server error: Check messages from the SQL Server\nDB-Lib error message 20018, severity 16:\nGeneral SQL Server error: Check messages from the SQL Server\nDB-Lib error message 20018, severity 16:\nGeneral SQL Server error: Check messages from the SQL Server\nDB-Lib error message 20018, severity 16:\nGeneral SQL Server error: Check messages from the SQL Server\nDB-Lib error message 20018, severity 16:\nGeneral SQL Server error: Check messages from the SQL Server\nDB-Lib error message 20018, severity 16:\nGeneral SQL Server error: Check messages from the SQL Server\nDB-Lib error message 20018, severity 16:\nGeneral SQL Server error: Check messages from the SQL Server\nDB-Lib error message 20018, severity 16:\nGeneral SQL Server error: Check messages from the SQL Server\nDB-Lib error message 20018, severity 16:\nGeneral SQL Server error: Check messages from the SQL Server\n") cmd_type=elb consumer=False name=tap-mssql--db producer=True stdio=stderr string_id=tap-mssql--db
2023-10-20T17:57:05.771235Z [info     ] time=2023-10-20 13:57:05 name=target_snowflake level=INFO message=Table db."table1" exists cmd_type=elb consumer=True name=target-snowflake producer=False stdio=stderr string_id=target-snowflake
2023-10-20T17:57:07.507385Z [info     ] time=2023-10-20 13:57:07 name=target_snowflake level=INFO message=Table db."table1" exists cmd_type=elb consumer=True name=target-snowflake producer=False stdio=stderr string_id=target-snowflake

@wesseljt
Copy link
Author

wesseljt commented Oct 20, 2023

aside from the specifics of the error -its weird the error has pymssql in it not pyodbc.

@BuzzCutNorman
Copy link
Owner

Looking at the error message it is referencing a tap-mssql--db. Would you be able to pass along that tap's config as well.

@wesseljt
Copy link
Author

should be that first one in the config above

@BuzzCutNorman
Copy link
Owner

I was able to replicate the issue. It seems once I remove the pip_url and variant items from the tap-mssql--db config inheritance started to work properly again. If those two config options are present and say driver_type is not in the config since it has a default the default is used which would be pymssql. Please try removing pip_url and variant from tap-mssql--db's config and let me know if things working as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants