Thank you for the update.

We all learn here. We try to give some of it back. It helps us all.

DDL = Data Definition Language.

i.e. your create table scripts.

Let me be the first to say I DON'T want my point pack!! 😀

Great question though. Anything that makes me think is a good question, regardless of the...

I assumed the OP was referring to data changes.

Of course change management should be used for any DDL/code deployment.

No.

If you need to be able to know who changed data in a table, you either need to have a trace running or set up auditing.

I'm guessing your table was imported from excel or access at some point.

Yes, if you plan to store 126M rows in a table, you need to do some serious optimization.

We need a create table DDL (you don't have data types). 😉

You may also need to filter with a WHERE clause on the table name (WHERE name like '%XYZ%') or whatever filter you might need.

EXEC sp_updatestats will work for all tables in the database

UPDATE STATISTICS tablename will run for just the one table.

SELECT CASE WHEN ROW_NUMBER() OVER (ORDER BY object_id) > 1 THEN 'UNION ALL ' ELSE '' END +

'SELECT * FROM ' + NAME + ' WHERE PROTOCOLNAME = ''ISUP'''...

Another suggestion would be to recompute statistics on that table on a regular basis, especially if you're adding 100,000 rows daily.

A NONCLUSTERED INDEX on SQL_POST_DATE might help if you don't have one.

Just set the Events Selection page to filter on the DatabaseName you want to capture.

EXEC msdb.dbo.sp_send_dbmail

Check BOL for the arguments you need.

We keep several servers sync'd hourly using this method. You can set up whatever shedule you like and you can change those schedules on the job if you like...