Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
SamC
White Water Yakist
3467 Posts |
 Posted - 2005-02-02 : 08:34:44
|
| I've always used Windows Explorer to search stored procs on my hard drive. It's fast, and has been a help identifying all references to a procedure, table or column.My prior laptop seemed to be unable to scan *.sql files. No error, but no results were returned.My latest laptop (fresh from the box) didn't have this problem, until recently. I'm sure it's got something to do with a registry entry that identifies the kind of files to scan.Does anyone know where to tweak search so it'll scan sql files again?Sam |
|
|
SamC
White Water Yakist
3467 Posts |
Posted - 2005-02-02 : 10:20:05
|
Solution found:Open Windows Explorer...Open the Search paneClick "Change Preferences"-- (Turn off that annoying animated puppy)  Click "With IIS Information Indexing Services"That's it. Windows search will search *.sql files now.Sam |
 |
|
|
SamC
White Water Yakist
3467 Posts |
Posted - 2005-02-02 : 17:33:31
|
| I was wrong. So I get to post a correction, and vie for the rights to the longest thread on SQL Team with all the posts coming from a single forum member.It isn't the IIS Indexing Service that reads the *.sql files. It's a registry entry 0|1 that filters files when set to zero.User Key: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\FilterFilesWithUnknownExtensions]set it to 1 (not 0)Had to restart windows for the value to take effect. Am happily searching sql files for keywords. |
|
|
|
SamC
White Water Yakist
3467 Posts |
Posted - 2005-02-02 : 17:45:31
|
And yet another post on this subject... quote:
>There are now way to get results when searching for a>word or phrase in a .sql file. If I rename the .sql file>to .txt , search is able to read the contents of the file.>It seems that XP ignore reading the contents for some>file extentions.XP Search for content works only on file types where the extension iseither registered as having only ASCII Text (eg .txt) or as having afilter to handle internal formatting codes and distinguish them fromUnicode (eg .doc). You can add a type as being ASCII text with thefollowing registry patch - which may not give sensible results if thefiles are *not* pure ASCII. This is set to sql - change .sql for othertypes. Also make a preliminary check with regedit that the subkeyconcerned does not already have a PersistentHandler for other purposes(sql is OK).Make the following, after - - start and before - - end into a file bycut/paste to NotePad. Make sure there is a blank line at the end. Saveas "Patch.reg" then d-click on this file to enter it into the registry.- - startREGEDIT4[HKEY_CLASSES_ROOT\.sql\PersistentHandler]@="{5e941d80-bf96-11cd-b579-08002b30bfeb}"- - end
This isn't the fix I used, but it took me so long to find this, I thought it worth posting for future reference. |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2005-02-10 : 01:54:55
|
| If you ARE running Index Server you may be able to search more quickly (but possibly less reliably) by prefixing the containing word(s), in Search Pane, with a "!" - this will cause Index Server to do the search, rather than Good Olde Sequential Search!Kristen |
|
|
|
|
|
|
|
|
Searching Stored Procs using Windows Explorer