Context: sql server 2005.
Hi I am not sure it's actually a log shipping issue because I am not a DBA. My boss told me our product database (A) is log shipped to another server/database (call it B) every 15 mins. I have seen the B and seen it being 'synchronized' (I forgot the word, I am not DBA. I am a BI developer on MS BI stack). The B is readonly. Recently my boss told me to write some views for reporting on B. But he didn't know it's readonly. Our company use both oracle and sql server and he is basically a oracle support manager (don't ask why, long story) and we don't have a dedicated DBA here (again, don't ask why). So because B is readonly, I googled and found below command
RESTORE DATABASE <db_name> WITH RECOVERY
I run it on B, and it's not read only anymore. Good I thought. Then came next morning, I found it stopped 'synchronizing'. It defenitely needs to be synchronized with A. So what I do now?
I have seen 'Transaction log shipping' in database property of A, and seen Backup schedule 'Occurs every day every 15 minutes....' but the 'Enable this as a primary database in a log shipping configuration' is not checked. So it seems not related. Then I found there is a job on B that using some third party cmd scripts that seems related to the 'Synchronizing'. And it reports error since the day I made the modification. So I guess I have to 'undo' the RESTORE DATABASE <db_name> WITH RECOVERY. How? I wouldn't bother asking my boss about these details, he knows nothing about SQL Server and he is new as well and this company has too much hidden histories which nobody knows.