live databases (MSSQL)
Posted on 2014-07-15
We are doing some risk assessment work on some older SQL Servers. There are a few instances that seem to be hosting databases that drive a number of differernt applications.
1) What potential risks are there here is storing databases from different applications on the same instance?
2) And can you think of any logic why an admin would set things up this way (typically cost cutting in this company!)
3) Is there any easy way to determine if these databases are live/being used? Where could you look for clues as to whether these databases are actively in use/being updated etc? Any queries which could help? Some may be orphaned and just never been removed.
4) Is there any risk in leaving old orphaned databases on a live database server?