Find text in sql modules

Question

Post reply

Find text in sql modules

Peter Shilovich

SSC Eights!

Points: 882
More actions
February 13, 2019 at 11:54 am

#381414

Comments posted to this topic are about the item Find text in sql modules

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

tamirgerber Valued Member Points: 69 More actions · Answer 1

One could use sp_msForEachDB builtin stored procedure. No cursor, no loop, and less chance to get into security issues.

Jeff Moden SSC Guru Points: 1004304 More actions · Answer 2

tamirgerber - Tuesday, February 19, 2019 6:51 PM
One could use sp_msForEachDB builtin stored procedure. No cursor, no loop, and less chance to get into security issues.

Not quite right. If you look at the actual code sp_msForEachDB and the procedure that calls, its a cursor/loop on steroids. 😉

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

tamirgerber Valued Member Points: 69 More actions · Answer 3

Jeff Moden - Tuesday, February 19, 2019 9:58 PM
tamirgerber - Tuesday, February 19, 2019 6:51 PM
One could use sp_msForEachDB builtin stored procedure. No cursor, no loop, and less chance to get into security issues.
Not quite right. If you look at the actual code sp_msForEachDB and the procedure that calls, its a cursor/loop on steroids. 😉

I am sorry for not being clear enough. My idea was that call of sp_msForEachDB eliminates a need to use cursor and loop explicitly. Less custom code - less headache 🙂

Peter Shilovich SSC Eights! Points: 882 More actions · Answer 4

tamirgerber - Wednesday, February 20, 2019 2:05 AM
Jeff Moden - Tuesday, February 19, 2019 9:58 PM
tamirgerber - Tuesday, February 19, 2019 6:51 PM
One could use sp_msForEachDB builtin stored procedure. No cursor, no loop, and less chance to get into security issues.
Not quite right. If you look at the actual code sp_msForEachDB and the procedure that calls, its a cursor/loop on steroids. 😉
I am sorry for not being clear enough. My idea was that call of sp_msForEachDB eliminates a need to use cursor and loop explicitly. Less custom code - less headache 🙂

Thanks for the feedback 🙂
I prefer not to use sp_msForEachDB here for two reasons. Firstly, becase of it is not documented. And secondly, this proc is intended to search for a text in user's DB.

Jeff Moden SSC Guru Points: 1004304 More actions · Answer 5

tamirgerber - Wednesday, February 20, 2019 2:05 AM
Jeff Moden - Tuesday, February 19, 2019 9:58 PM
tamirgerber - Tuesday, February 19, 2019 6:51 PM
One could use sp_msForEachDB builtin stored procedure. No cursor, no loop, and less chance to get into security issues.
Not quite right. If you look at the actual code sp_msForEachDB and the procedure that calls, its a cursor/loop on steroids. 😉
I am sorry for not being clear enough. My idea was that call of sp_msForEachDB eliminates a need to use cursor and loop explicitly. Less custom code - less headache 🙂

Ah. Got it. Thanks for the feedback.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Jeff Moden SSC Guru Points: 1004304 More actions · Answer 6

Peter Shilovich - Wednesday, February 20, 2019 3:06 AM
tamirgerber - Wednesday, February 20, 2019 2:05 AM
Jeff Moden - Tuesday, February 19, 2019 9:58 PM
tamirgerber - Tuesday, February 19, 2019 6:51 PM
One could use sp_msForEachDB builtin stored procedure. No cursor, no loop, and less chance to get into security issues.
Not quite right. If you look at the actual code sp_msForEachDB and the procedure that calls, its a cursor/loop on steroids. 😉
I am sorry for not being clear enough. My idea was that call of sp_msForEachDB eliminates a need to use cursor and loop explicitly. Less custom code - less headache 🙂
Thanks for the feedback 🙂
I prefer not to use sp_msForEachDB here for two reasons. Firstly, becase of it is not documented. And secondly, this proc is intended to search for a text in user's DB.

Totally understood.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)