Heh... it's funny... I see so many people saying that people who are resistant to change are stuck in a rut.  I guess it's never dawned on those people that...

Note to self: PPTS.

The problem is very likely that you're simply not doing any log file backups.  Full backups do nothing to clear the log file.

If you want to be able to do...

You need single quotes around the data that you're passing for @tempdata.  I've added them in Red... one before the starting bracket and one after the ending bracket.  Otherwise, your...

The method that both Ken and Phil are using is an arcane method known as a CROSSTAB and is a much more flexible manifestation than a PIVOT.

You can read more...

Another name for "conditional aggregation" is a CROSSTAB.  MS use to carry a full entry in BOL on it until they came out with PIVOT.  You'll be able to tell...

Publish well written standards, Enforce them. Period.

I leave it at FULL because my database backups will try to do log file backups on any database not in the SIMPLE recovery model.  That proc is also setup...

Honestly not fussed on the harshness of response if it contributes to moving the discussion forward - obviously meant in good humour.

It does sound like there are different opinions...

I also put something like that together where it would look like this

where ([definition] like '%INTO [tableName]%' or ([definition] like '%update [tableName]%')

That got me the closest...

Heh......

It also sounds like a possible "connection leak" in the applications that are hitting the database.

Unfortunately, I don't have a say about the structure of the table. It's populated via an ETL process. I just want to create dummy data for testing so want...

You could just search the "definition" column of sys.sql_modules for the table name with the understanding that it won't find ad hoc queries.

The real key here is... are people going to carry you down the hall on their shoulders if you make any changes here?  If not, I'd leave it all be. ...