Batch rename of queries ?

Question

We are starting our upgrade of HCM 8.9 to HCM 9.0. Our end users have written over 10,000 queries with very little naming convention - usually just starting with their initials. Our University is 'Sonoma' so we want end-users to rename the ones they want to keep to start the first 4 chars with 'SON_' and make them public. This way as the DBA my job is easier to put them into a project and move them to 9.0. end-users complain that it's 'too much work', because some of them have written hundreds of queries.
Is there a way to batch rename them using a SQL script - the problem I see is that there are many query tables they exist in, eg, PSQRYDEFN, PSQRYFIELD, PSQRYRECORD, and many views also so I am worried that trying to rename them by adding 'SON_' to the beginning would miss some tables and screw things up.
I would be interested to hear other folks query strategies during upgrades.
Thanks,
Allen Cunningham
DBA Sonoma State University

Answer 1

I guess my first response would be, Do you really want 10,000 public queries? In our environment only the development team and those functional users that are associated with the development team have the ability to create public queries. Once a query is made public, it's the development team's responsibility to support it. No doubt you've got at least a couple of users that have created some poorly written queries. You probably don't want to support those.
Secondly, upgrades are a time for clean up. At the very least I think I would go ahead and ask them to review their own queries. If they find that they have a query that is useful to other users, offer to make that public for them and have the team support it. I would also have them consider deleting queries that they no longer use. In reality, we didn't care about the naming conventions for private queries. The whole idea of the convention is to be able to separate our queries from the delivered ones. With private queries it's pretty easy to make that distinction.
Third, I would categorize the queries more than just prefixing them with your organization. We are on an HRMS version so our queries are prefixed by HR, PR, TL, BA, etc. A little more categorization to the queries should be helpful so you don't have to scan 10,000 queries for the one you are looking for. Of course I would only do this for the public queries.
In our upgrade from 8.3 to 9.0 I ran each of our public queries for efficiency and validity. It was over 1,000 queries and took several weeks to get through them all. After that we went back to some of our power users and offered to assist them with queries that would no longer work (i.e. tables that no longer existed in the system).
One final thought. Have the users make the changes in your existing production database now. During our upgrade some effort was made to rename production queries. In one of our final copies of production we had these new queries come in that we had to redo simply because the name had changed.