16,017,015 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View .NET questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by Basavaraj P Biradar (Top 2 by date)
Basavaraj P Biradar
19-Nov-11 2:18am
View
Deleted
Just one comment, as sql_modules will have row's only for Objects of type P, RF, V, TR, FN, IF, TF, R and D. So, the object types such as U, X, S, L etc... mentioned in the case statement are irrelevant and they may mislead. If possible please take out the irrelevant object type's mentioned in the case statement.
Basavaraj P Biradar
26-Oct-11 11:29am
View
Deleted
In some rare cases this query will return in-correct result, because in syscomments table the text column is of type nvarchar(4000). If the sp text is exceeding this limit, sp text is split and stored in the multiple rows, and if the seach string is at the spliting position, then search will fail to return such stored procedure name.
Also in the query you are not getting the sp content and that is the reason you are assuming it is much faster. But when I executed below query, found that it is much slower and also leading to lot of logical reads also...
SET STATISTICS IO ON
SET STATISTICS TIME ON
SELECT DISTINCT so.name
FROM dbo.sysobjects so
inner join .dbo.syscomments sc on so.id=sc.id
WHERE so.xtype='P' AND sc.text like '%SearchString%'
SELECT OBJECT_NAME(object_id)
FROM sys.procedures
WHERE OBJECT_DEFINITION(object_id) LIKE '%SearchString%'
SET STATISTICS IO OFF
SET STATISTICS TIME OFF