Hi all,
Apologies if this has already been discussed elsewhere - but I am just hoping to get a little bit of feedback on how organizations with non-standard naming conventions for local objects have renamed them for the Customizations Review in preparation for v.11.
I know the review only looks at objects beginning with L signifying Local - and we unfortunately have some named differently. Have others in this position simply Right-Clicked and Renamed the Procedure and the instances in which other items call upon it? I'd rather go this route as it seems so much less time-consumptive.. But have seen warnings against doing this, and suggestions to Drop and Recreate Procedures under a new name.
Advice or stories welcomed, thank you!
Frannie
Hey Frannie,
Definitely don’t rename any procedures as they are most likely being called from elsewhere and this will (in short) break things. What you can do though is copy the procedure MP_review_customizations and alter your copy so that it looks for more than just 'L%'. Below you can see where I added ‘PUB%’ and ‘NYSF%’ to the mix for us:
For Stored Procedures:
WHERE [text] LIKE @cur_like
and ((OBJECT_NAME(id) like 'PUB%' or OBJECT_NAME(id) like 'L%' or OBJECT_NAME(id) like 'NYSF%')
For Local Tables:
where COLUMN_NAME like @cur_like
and ((TABLE_NAME like 'PUB%' or TABLE_NAME like 'L%' or TABLE_NAME like 'NYSF%')
In terms of copying the procedure, I just saved it as a file and didn’t make a new procedure because no-one else here needs to look at it in detail. Do you need others to be able to run it from the client? If you do, I don’t think there is any harm in updating the original procedure in this circumstance, but someone please tell me if this is a no no.
Tash
Thank you Tash! This totally makes sense. :)