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

Avoid parsing other connections type than SQL Server #28

Open
fpatou opened this issue Sep 12, 2018 · 1 comment
Open

Avoid parsing other connections type than SQL Server #28

fpatou opened this issue Sep 12, 2018 · 1 comment

Comments

@fpatou
Copy link

fpatou commented Sep 12, 2018

hello,

Error log show many 46010 error coming from MDX or Oracle...(as package connect to mutiples environments)

Would it be possible to avoid parsing sqlstm from other origins than SQL SERVER ?
Regards

@keif888
Copy link
Owner

keif888 commented Sep 14, 2018

This is possible, but, you will still get issues where an ODBC or ADO connection is used, as these could be SQL Server, or something that doesn't use TSQL.

I'll see if I can get the parser to better handle non TSQL, vs not understanding a TSQL statement.

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

No branches or pull requests

2 participants