ok since you are inserting into a table, you do not need the ORDER BY in the end.

You could fiddle with changing it to use EXISTS instead of...

i would think about slicing the new SAN into three drives; two big ones for the SQL stuff for db and logs, and a new,smaller one for the disk-based packages.

I've done this with a script task in an SSIS package. it is a good size snippet of code, with lots of caveats.... the end result is exactly what everyone...

Yes, you'll end up needing  bunch of case statements, one for each column.
This could also be done int he presentation layer, so for example SSRS could use an expression...

With the exceptions of indexes created as part of a primary key or unique constraint, then no. SQL does not save the creation/modify date of indexes. you can get the...

this page specifically says, for SQL 2012, no retirement for exams are planned at this time:
http://blog.firebrandtraining.co.uk/2017/01/microsoft-exams-retiring-2017.html

SQL Server

As with SharePoint, we see only the planned retirement...

you are correct.
SSAS can participate in a Cluster with shared storage, and is Cluster Aware.
but  the service does not  have the equivalent of Availability groups.

don't test on production.
best practice is to test on a Development copy of production,s o you have no chance of actually screwing up important data.
never test on production.

yeah now that we see the actual execution plan, we can see the impact of the nested views; there's a couple of tables like [ins_smr] and [ins_mod] that are joined...

for me, your expression looks like the problem, but of course it depends on your data.
=IIf(Fields!NotificationType.Value = "Discharge",False,True
that is evaluated each row, right? so potentially some rows toggle...

I'd look at the indexing and SQL code in the view; it could be using non-Sargable WHERE statements or join criteria, inline scalar functions, or just not have any indexing...

create a table with the same schema as the table you want to audit.
add additional columns for capturing whodunnit information.
then you just need a trigger to handle update...

somone already mentioned that the order by , when inserting into a table is an extra cost with no benefit;(a table has no implicit order...you have to use an order...

here's your data setup with proper data types. your monthYr MUST BE a date datatype in order to get the proper order. you don't want the data to order in...