Hello,

I can't remember if the search feature in the DDT ever worked for me, but when I type something into the Find field and click on the search button, nothing happens... and all of the search options are checked.

???

Funny, I had never seen this Search feature.

Anyway, I tried it over here and could reproduce it. It did work on my own Views and Stored Procedures, but wouldn't find anything on the Tables, for example.

Hi Ivan,

I don't think it is designed to look into table fields, at least that is not one of the options in the "Search Options"


Hmmm, I believe I never had the need to search for a field name, all the time for view names, a field in a view, stored procedure, etc.  Anyway, very useful feature.

Edhy Rijo

Hey Edhy!

Yep, that could be it.

Abraços.

I'm using v7.6.0 of the DDT, and I'm searching on RAISEERROR.

I have a ton of code in our database with the old RAISEERROR syntax which no longer works in SQL 2012, so I was hoping the find feature would be a quick and easy way to see how many lines of code that need to be touched.

But, when I search, nothing happens at all...

What search term can I use to verify if the find feature is working at all?

Hi William,

Make sure you have checked all the options in the "Search Options" as shown in my previous thread.

Edhy Rijo

Yes, I confirmed that in my original post.

Thanks.

Will the search find other things, or is it just RAISEERROR that isn't being found?  If you search for a field name or part of a field name does it find anything?

Table names - nothing

Field names - nothing

Code within triggers - nothing

Code within stored procs - results

Funny thing, if I clear out the search term after results from stored procs are found and search again, I get the stored proc results again, and user defined functions.

I just checked the dbo.Search_Query sproc, and it certainly doesn't check triggers.  It only checks sprocs, functions, views, and deploy scripts.  That's the bad news.  The good news is that you can easily modify the stored procedure to return the extra results if necessary.  You won't be able to double-click a trigger from the list and open it for editing, but at least it would return it in the results.  You would need to edit the Search_Query sproc and add this before the "RESULT SET #1" comment at the bottom of the procedure:

Thanks for the reply.

Will this be incorporated into the next DDT version?

Oh yes.  The search on the next DDT will be vastly expanded.  The search on the current version was more of an afterthought.