All Data Transformations via SSIS Some folks here at my current job have made the decision that all data transformations that go into our database must be done via SSIS. This means that any old code such as views, stored procedures, functions, etc. that are used to transform data will no longer be used. The transformations they currently perform will be done via SSIS only. I am trying to come up with a list of potential issues we may face and I don't know as much about SSIS as I do about SQL Server being that I am a DBA here. One of the issues I see is attempting to look at performance issues in SSIS vs sql objects. What are the other things I am missing? We are using Microsoft SQL Server 2016 SP2 and SSIS 2016.
I have seen this done.  And while it's not something I would ever recommend, it does have some advantages from a process and skillset point-of-view.  The main reason you would try this is to have a consistent drag-and-drop process for building, and importantly, changing ETL processes.

Issues:

1) Performance.  Performing transformations in SSIS data flows is just slower than using TSQL.  

2) Productivity.  Using TSQL is, perhaps, a more difficult skill, but for someone who can do both, it's massively more productive to build and test using TSQL than SSIS data flows.