We also have good enterprise SAN (vmax) with many fast spindles, RAID 10, flash caching, fibre-connected.

In my cases, most workloads are cross-database. So we capture activity either at a gross "everything" level, or more often, just at the specific workload level.

I think this works:

--first part gets events within the date range

SELECTevt.*

FROM dbo.#Events evt

WHERE evt.ProcessDate BETWEEN @StartDate AND @EndDate

--second part gets related events that occurred before

UNION...

Peter, I think you're on right track, but there is a flaw. The initial sample data does not show it, but when used with date range of 6/12 -...

I like Luis' answer. A different approach, likely with a different query plan which may be more or less efficient depending on your data/indexes, etc is this:

...

We've been using 25MB or 100MB file size for years now, for traces ranging from 10MB to 5GB in total size. Haven't had any problems with these file sizes....

I get that. The value that goes inside single quotes here: @parameter_name=N'[User::Cycle]' must be a value that you can lookup in table SSISDB.internal.execution_parameter_values. Can you confirm that you've...

I see a few of these every week, usually around same time that I know our security team is performing white-hat testing.

Have never seen these as indication of...

If the 2012 target can be unreadable, then you can log-ship. That is process we used to migrate from SQL 2005 to SQL 2012, was very straightforward.

If...

what I added above applies to a single replica, not all replicas.

If you removed the DB from the AG on the primary...that would remove it from all replicas....

You can easily remove a single DB from an AG secondary replica, and then add it back. I've mostly used SSMS GUI for this, but I'm sure the TSQL...

I think the INI files are useful. You're right, there is a lot more to do after SETUP finishes. Checkout a codeplex tool called SPADE, helps with the rest...

It will work. You restore DB (full, diff, txlog, whatever) on your primary AG node, then re-sync the secondary replica(s) like you did back when you added the DB...

you just need to terminate line before the THROW with a semicolon, then it will work wherever you want to put it. In this case, ROLLBACK TRAN;

This message is returned by catalog.set_execution_parameter_value raising error 27176 when it fails to lookup your parameter in SSISDB.internal.execution_parameter_values.

Are you able to successfully call your stored procedure from a...