Are you referring to agent jobs running SSIS packages - and only those types of agent jobs?

If so - why are you manually modifying and running agent jobs in the...

Are you sure those 'steps' are running?  If they are running through an agent job - verify the agent job is not configured to look for the SSIS package on...

I will add a few more points to consider:

1. In a 3-node cluster - where one of the nodes is in another data center, what happens if you lose connectivity...

It depends on how the cluster is configured - and whether or not that witness is needed to maintain quorum.  If you are configured as node majority with a witness...

One option I have used for these types of requests is an SSRS report.  Then give the users access to the report and they can export to whatever format they...

I am also curious - is this a situation where you upgraded SQL Server and the vendor has not certified their application for that version?  In other words, the vendor...

I would reinstall the SSIS extension - the data tools does not contain the SSIS extension.

If you need near real-time access to the data for reporting - then your only option is going to be replication.  All other options result in a point-in-time solution.

If you...

I inherited a turd environment.  Many, many years of neglect. All to say that I have no idea why things are set up the way they are.  I'm just...

Just curious - why would you have a secondary replica that is not configured the same as the primary replica?  If you failover to that secondary and it isn't the...

It isn't clear from your description what you are asking.  I assume by active/passive you mean an FCI (Failover Cluster Instance) where you have 2 or more nodes clustered with...

Have you tried running an integrity check on that database - or DBCC CHECKTABLE for that table?  That would be the first thing I would do to verify there isn't...

I would recommend moving that 'share' to a different location - and not on the C:\ drive of the SQL Server instance.  The location you have listed is also considered...

You can try one of the following:

WHERE server_principal_name <> 'myDomain\!sqlmonitoring' AND server_principal_name <> 'myDomain\myDomain\myServiceAccount''

WHERE NOT (server_principal_name = 'myDomain\!sqlmonitoring' OR server_principal_name = 'myDomain\myDomain\myServiceAccount'')

If my assumption about the eligibility column is correct - then I would next recommend a persisted computed column on that table as: SUBSTRING(eligibility_ud, 1, CHARINDEX('-', eligibility_ud + '-', 1)...