How to check for invalid triggers and procedures?

[Jeremyjm]

Hello,

Our software manufacturer wants us to check for invalid triggers and procedures against our SQL Server 2000 database. Can someone please school me on how this is done? Thank you.

-Jeremy

 

[ca8msm]

How do you define "invalid"?


-------------------------------------------------------

Mark,
[URL unfurl="true"]http://aspnetlibrary.com[/url]
[URL unfurl="true"]http://mdssolutions.co.uk[/url] - Delivering professional ASP.NET solutions
[URL unfurl="true"]http://weblogs.asp.net/marksmith[/url]

 

[onpnt]

Yeah from what you said the best answer is, make sure you didn't write crap and put it on your instances.

[sub]____________ signature below ______________
Backups are for sissies!!!!

http://www.lessthandot.com

coming to your keyboards soon[/sub]

 

[Jeremyjm]

Good question. I'm thinking they're referring to manually created triggers or procedures that aren't compatible with their latest version but we haven't created any.

 

[onpnt]

so you're asking us if your company violated the license agreement with some third party software?

only you or the people that put any unauthorized objects on the database will know that. there is no miracle method to finding things that shouldn't be there unless you want to install a fresh DB from the company and compare it with the "customized" one

[sub]____________ signature below ______________
Backups are for sissies!!!!

http://www.lessthandot.com

coming to your keyboards soon[/sub]

 

[Jeremyjm]

Yep, I guess that was their way of asking that question. It kind of caught me off guard but I called back and gave them a firm no and now they are actually troubleshooting my original problem.

Thanks for the help.