Recently I encountered an issue while trying to reinitialize transactional replication subscription through backup and restore method due to timestamp column in a published table. In this article, we will discuss about the relation and the impact of timestamp column with SQL server replication.

Introduction Rebuilding the MSDB database process: First we need to verify the reason of failure in the SQL Error logs or windows logs and troubleshoot accordingly. If database is corrupt then please restore MSDB database same as a normal user database if backup is available 2.) If We don’t have the latest backup or any other backups, then please stop the instance and start the instance in Single(maintenance mode) and trace 3608 in startup parameters.

This blog discusses the steps to determine the user responsible for truncating and removing data from tables on MSSQL server, and identify the entity responsible.