Stored Procedures and Local Procedures

John,

I am sure the community can comment on their experiences so far but I did want to make sure you had all the network resources as well.  We have documentation and a recorded learning on preparing customizations for v11.  The recording and document will outline how to use the tools provided to help with customization review as well as a starting point for the approach.  In addition the Version 11 Tips and Tricks webinar includes a section on customizations; as a part of this session Yale also shared their customization preparation worksheet.  

Best,

Anna

One of the reports mentioned in the Preparing_Customizations_for_Tessitura_V11 doc called ‘Migration – V11 Customization Review Report’ is run from the stored procedure MP_REVIEW_CUSTOMIZATIONS. It more or less looks at all local procedures and tables that start with ‘L’ and scans for certain things (like N2). Not all of ours started with ‘L’, so I adjusted the criteria to include our naming conventions also.

As is states in the doc, it doesn’t look at everything, including any SQL you may have manually written in job steps. I got an output of all of our jobs and their steps using tables from msdb and then manually did ‘Ctrl F’ in an excel and scanned over them for things that may cause issue. Luckily we didn’t have many jobs with SQL written directly in them so this task wasn’t hard! Happy to share code if you like.

I also had each department rate our custom reports from ‘Business critical’ down to ‘Don’t use anymore’ for prioritizing. There is another report called ‘Migration - Custom Report Run Frequency’ which was great for helping everyone with this. As far as making the adjustments, we have chosen to use the bridge views where possible and will look at the wonders of V11 reporting once we are up and running and everyone is more comfortable with the new functionality. Still very much a WIP and I’m not that far down the rabbit hole yet, but it seems to be going smoothly so far.

Hope that helps!

One of the reports mentioned in the Preparing_Customizations_for_Tessitura_V11 doc called ‘Migration – V11 Customization Review Report’ is run from the stored procedure MP_REVIEW_CUSTOMIZATIONS. It more or less looks at all local procedures and tables that start with ‘L’ and scans for certain things (like N2). Not all of ours started with ‘L’, so I adjusted the criteria to include our naming conventions also.

As is states in the doc, it doesn’t look at everything, including any SQL you may have manually written in job steps. I got an output of all of our jobs and their steps using tables from msdb and then manually did ‘Ctrl F’ in an excel and scanned over them for things that may cause issue. Luckily we didn’t have many jobs with SQL written directly in them so this task wasn’t hard! Happy to share code if you like.

I also had each department rate our custom reports from ‘Business critical’ down to ‘Don’t use anymore’ for prioritizing. There is another report called ‘Migration - Custom Report Run Frequency’ which was great for helping everyone with this. As far as making the adjustments, we have chosen to use the bridge views where possible and will look at the wonders of V11 reporting once we are up and running and everyone is more comfortable with the new functionality. Still very much a WIP and I’m not that far down the rabbit hole yet, but it seems to be going smoothly so far.

Hope that helps!