Is there a relationship between the number fo table definitions in the repository and the impact on performance of the jobs?
I can think that the repository which stores everything will be impacted and that at a minimum job start-up time will be impacted, but will the runtime of a job be impacted?
I'm trying to motivate for a cleaner table definition space. I'm sure everyone will agree that the following is useless:
Category: Saved
Data Source: Aaaaa
Table Definition: _aaaaaaaaaa
![Mad :x](./images/smilies/icon_mad.gif)