Is your SQL environment growing so big and intertwined that your memory cannot tell you right away which SSIS package is populating which tables, and witch tables are used by which SSRS reports, and which SQL job is executing which SSIS package or procedure? Welcome to the real SQL world!
A DBA in my group has built a few life-saving tables populated daily by a few very slick SSIS packages. Now I can search anything that my memory cannot reach.
The basic format he used is:
For searching a SSRS report, it’s a little less straightforward.
To be continued on this topic.
Tags: ETL BEST PRACTICES,