-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Encrypted SQL objects causing issue.. #16
Comments
Hi, Thanks for reporting this, the problem is that we can't ask sql for the definition as it is purposely hidden/encrypted. I will add a check so that it doesn't crash and fail everything so it is at least handled gracefully and any unencrypted procs are covered. Ed |
Hi - this should stop it crashing, we can't decode encrypted procs but at least any unencrypted code will be seen: https://github.com/GoEddie/SQLCover/releases/tag/v0.4-test |
Hi, still v0.4 does not solve the issuewith encrypted object still we are getting same errorException calling "Stop" with "0" argument(s): "Unable to cast object of type 'System.DBNull' to type 'System.String'."
|
Hi, There are only two places that could cause this - I fixed one of them with that release and the other would mean you have an object in sql that doesn't have a name. If you run: select object_id, '[' + object_schema_name(object_id) + '].[' + object_name(object_id) + ']' as object_name, definition, uses_quoted_identifier from sys.sql_modules where object_id not in (select object_id from sys.objects where type = 'IF') do you have a value in every object_name column? ed |
Hi Ed, thanks for the quick response, yes the above query returns my encrypted object_name. |
If any of my SP's/Functions are created as Encrypted, while stopping it gives me error as.
(as a work around deleting encrypted objects.)
Exception calling "Stop" with "0" argument(s): "Unable to cast object of type 'System.DBNull' to type 'System.String'."
At C:\Tools\SQLCover.ps1:106 char:17
Thanks
Vidhyashankar
The text was updated successfully, but these errors were encountered: