7 results found
It would be lovely to find other elements in the database that may not stop it from working right now but are 'problems waiting to happen'. Other examples might be to search for field names that clash with reserved terms.11 votes
When you are working with a rather large database it would be nice to be able to save a list of invalid objects to come back rather than having to re-run through the entire database again.6 votes
Please could you add an option to check for invalid objects in multiple databases and to be able to export the results in either a single file or 1 per database. It's a real pain doing 1 at a time and manually selecting the results to do a copy/paste.4 votes
It would be helpful if you would add an option to check if the objects used in a stored procedure really exist when creating it.
CREATE OR ALTER PROCEDURE [dbo] [SelectFromTableThatDoesNotExist].
SELECT * FROM [dbo] [NonExistingTable];
The table used in the procedure does not exist, but the procedure can be created without errors. In this case, it would be desirable if SQL Prompt had an option to output an error when creating the procedure.3 votes
If any stored procedures in the database are encrypted then "Find Invalid Objects" will get a null reference and prompt to restart SSMS.3 votes
using LocalDB, the database path names can be rather long, and in the Sql Prompt Invalid objects UI, there isn't a way to expand the database name, no pull handles or widening of the screen doesn't change the comboboxs dimensions which makes it hard to find the one I need without clicking through each one.2 votes
The Database drop down needs to be dynamic in width or allow us to pull it wider. It is extremely difficult trying to find the database I'm working on when I have multiple installed in a LocalDB environment.1 vote
- Don't see your idea?