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

Error Number: 46010 #37

Closed
CarlienM-discovery opened this issue Apr 4, 2022 · 5 comments
Closed

Error Number: 46010 #37

CarlienM-discovery opened this issue Apr 4, 2022 · 5 comments
Assignees

Comments

@CarlienM-discovery
Copy link

Hi there. Any idea why I get 100's of 46010 errors when running the dependency analyzer?

@keif888
Copy link
Owner

keif888 commented Apr 4, 2022

The Parser that is being used is Microsoft's Parser that SSDT uses.
There are a number of bugs within that Parser that have been fixed over time, but this project hasn't been updated to use the fixed parser.
eg.
https://developercommunity.visualstudio.com/t/ssdt-incorrectly-highlighting-syntax-issue-sql4601/790403
And this one is still open:
https://developercommunity.visualstudio.com/t/iif-in-codition-sql46010-incorrect-syntax-near/1578715

Without an example of an SQL Statement that is causing the issue to be raised, I'm unable to confirm this.

@keif888 keif888 self-assigned this Apr 4, 2022
@keif888
Copy link
Owner

keif888 commented Apr 11, 2022

I've assumed that the issue is ODBC call's to stored procedures.
This is fixed in https://github.com/keif888/SQLServerMetadata/releases/tag/v0.28.0.0-beta

@keif888 keif888 closed this as completed Apr 11, 2022
@CarlienM-discovery
Copy link
Author

Thank you . I will check today. Have been just snowed under with work :-) Thanks again. Much appreciated.

@CarlienM-discovery
Copy link
Author

Thank you. I have reinstalled - still getting some errors. Will look if i can do some analysis later today. From just watching the parsing - it might queries running on Oracle. Let me do some work on this. Thank you once again.

@CarlienM-discovery
Copy link
Author

Checked - it seems it is an issue with our scripts. "SQL Server does not support CURRENT_DATE function" A lot of our devs are previous Oracle devs and use "current_date" everywhere :-) Thank you for all the effort on your side.

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