It has come to my attention that we have quite a number of reports on our Reporting Services website that depend upon local tables created for that one purpose that unfortunately do not conform to suggested Tessitura taxonomy (i.e. do not start with LT_LOCAL_TABLE_BLAHBLAHBLAH). In light of the pending v11 upgrade, must I rename all of those tables to include the LT in the name so that the upgrade code knows to pick those tables up and bring them into v11 with the others, or risk them being ignored/dropped?
Obviously, I'd like to avoid such a tedious and time-consuming endeavor if possible. Perhaps this would be the time to make stored procedures for them so I can leave physical tables out of it all together, eh?
Thanks, Tessiturians.
Matt,
Any time you use local tables or other database objects which do not use the standard database naming conventions, you do run the risk that the upgrade will overwrite those objects. As part of the v11 upgrade there are no sweeping changes to the database which would remove, overwrite, or 'not bring over' your local tables but there is no guarantee unless you are using the proper local table names. So, that all being said, I would make a long term plan to update the local tables to the appropriate naming convention but you do not necessarily have to complete that project in advance of the v11 upgrade. For v11 you will need to test those components carefully to make sure they were not affected by the upgrade if they have not been migrated to the new naming.
Best,
Anna