We had SQL RAP and we got warning that Transaction log files larger than the database files. They advised me to remove databases from Always ON , change recovery mode to SIMPLE and then shrink log files and put it back to Always On. And change maintenance plans. T-LOG backup is running every hour. But again next day transaction log files are larger than the database files. As this is running SharePoint 2013 databases, they said it could be do to the migration of SharePoint 2010 databases to 2013, but I have same behavior on another Always on cluster which is not SharePoint. I have tried also to implement Ola Hallengren's maintenance script with same results. On other machines without AO there is not such problems. So I am not sure why is this happening, is it related to Always On? I know that Always On AG Databases Need bigger Log files, so would this be normal behavior in AO? Thanks