I inherited a collection of Instances/ MS SQL Databases/ SSIS scripts on a server. I am now the interim "accidental DBA."
I thought I was familiar with everything there, but apparently not. It's all completely undocumented.
I myself am not even currently the 'master admin' of the -- well ... I'm not even sure how that works. Can you group all instances on a server together to have the same master admin account? It's possible one of IT guys who knows nothing of the contents of these dbs has root access of some sort.
Let's just say -- I'm familiar with probably 80% of all processes that go on in this server. It's a collection of databases and SSIS scripts.
HOWEVER, I have noticed that some tables --- well, WHATEVER is writing to them, I have no idea. I don't have visibility to the (presumably SSIS since everything else is SSIS) scripts that are writing to them.
The few SSIS scripts I do have visibility to --- well there's a different "collection" for every Instance on this server.
Well - anyway -- there may be an IT contact that has root access/ admin access to something. The old DBA is gone.
Assuming this IT contact has top-level access to every Instance/ Database on this server, should I just access him for a high-level mapping of every instance-database and potentially access? (I'm literally the only one working with these databases). A lot of stuff I do not have access to, I'm either unaware of its existence, or its hidden.
What happens if this IT contact does not have admin access to some "pieces" or databases here? Are we screwed?
Should I request remote access to the actual Server (probably Windows Server 2012) that this database is hosted on? I'm wondering if that would help me investigate/ find where these Mystery SSIS scripts are.
How do I find out what robot-script is writing to a bunch of tables? Should I set up SQL Server Profiler? I guess it's called Extended Events now? What access/ permissions are required for this (I assume I just need trace permissions on the database where the tables are being updated)? Again, I'm well aware of the database where the updated tables are located --- there are SSIS scripts in that Instance, but none that write to these tables. Some "Mystery Process/ Script" is doing so daily.