Normally you'd just specify a default value rather than having to use a trigger for that.

For example, say you have table "tableA" that you want to add a default value...

You can adjust the SUM(s).  I wasn't sure if you wanted to list only the net or all three; if you want only the net, remove the first two "OH"...

I admit that for Medicare patients, as specified by the author, SSN might be valid to use (to be eligible, a person would need an SSN (or perhaps a TIN)). ...

More specifically, if you need to fully shrink a log, do something like this:

--assume you want log to be 3GB after shrink
USE database_name;
DBCC SHRINKFILE(2);

--explicitly increase the log...

Change the size to a fixed MB - then shrink the file to as...

Change the size to a fixed MB - then shrink the file to as small as...

SQL can usually imbed the conditions into the query plan to access the table rather than scanning the entire table first.  Of course you'd have to look at the query...

This does look like something maybe outside of SQL Server?!

Although, in order to truncate the log, a checkpoint must be taken after backup.  So step 4b. should be a CHECKPOINT,...

Yes, the script is 100% safe to run in a prod environment.

It does change a couple of settings for max efficiency, but first it captures the current settings and reinstates...

That looks far more like what I would expect (even with only 2 days' worth of activity).

I can tell you that (1) you have the correct clustered index (2) I...

Not much showing.  Only thing you can really do for now is REORGANIZE the columnstore index(es).

Unfortunately there's very little activity against this table shown in the stats -- no more than 5 days' worth of activity.  Either SQL was restarted or a change was made...

Was the first result set empty??!

Not nearly enough to go on to analyze indexes.

If you'll run this script and post the two results from it, we can go further from there.  PRIOR to running, be...

SELECT 
  p.name AS [Plan], --<<--
--everything else same as before--