Change recovery model while the database is in replication
We have a production database that is in full recovery mode. This database is being replicated to another server. (transaction replication) We have maintenance jobs run on Friday nights which include index rebuilding. Transaction log backup files are huge after this maintenance job. So I am thinking of changing the recovery model to simple before the maintenance job starts and change it back to full after the maintenance job. Will this method impact the replication? I know replication can work with any recovery model but not sure whether switching recovery models full to simple and then simple to full will have any impact on replication? Any help/guidance will be much appreciated. Thanks.
I know replication can work with any recovery model but not sure whether switching recovery models full to simple and then simple to full will have any impact on replication? Replication is not dependant on recovery model.Log reader agent scans the log and inserts them as commands in distributor database ,at this point of time only,the log will get truncated(space can be reused). So even if you change recovery model to full or simple,those settings won't affect replication and are not replicated
Using date parameter in SQL Server CTE
Persisting Data To SQL Server via ASP.NET MVC
Will SELECT become slower if I include a second non-indexed column in the query?
How DATEADD(DAY,1,TIMESTAMP) SQL in WHERE
Find name using like operator in SQL Server
Microsoft SQL Server: wrong query execution plan taking too long
Best way to handle updates on a table
Retrieving XML Data from sql server
Azure Recovery Vault Backup is failing for SQL VMs
excel via for Mac 2011 SQL Server
multiple declare statements with one creating a temporary table
SQL Query is taking infinite time when using with order by
SAS query issue on external DBMS TABLE where Column Name has space
Try-Catch with Stored Procedures in SQL server
Is there an analogy between a recursive SQL query and a recursive function?
stored procedure 'auto_pk_for_table' not found