SQL Server Management Studio could not save the configuration of as server a Secondary

Dear All,
Day before yesterday when I was implementing Log Shipping on my production server then I got a new error which was “SQL Server Management Studio could not save the configuration of as 192.168.1.101 a Secondary. (Microsoft SQL Server Management Studio) “.
I did search on Google for this but unable to find solution then at last I just got an idea from SQL Server central’s forum http://www.sqlservercentral.com.
I just ran following command
SELECT   @@SERVERNAME ,  serverproperty(‘servername’)
Select * from sysservers where server_id = 0
What I found the server instance name was different then Machine name. In general we keep machine name and SQL server instance name same.
So I got impression to change SQL Server name for this I did following steps

1) Run  SQL statement   sp_removeserver “servername” to  remove  existing server name
2) Run  SQL statement sp_addserver “serverName”,Local to add new server name
3) Restart  SQL server Services
After this I tried SQL Server Log shipping, it was implemented successfully.

Thanks & Regards
Rajat Jaiswal

Advertisements

How to resolve Log Shipping Error “Exclusive access could not be obtained because the database is in use.RESTORE LOG is terminating abnormally”?

Hello Friends,
This error normally came when you did log shipping on your database and  your secondary server database in stand by  mode.
In this error your secondary server database restore job will not work. To resolve this error you just need to change the log shipping setting.
When you configure secondary server database mode   there is check box which says disconnect all collection at the time of restore database so just check that check box and you will find your log shipping is working.

Thanks

Rajat

How to shrink Log File when Log shipping is implemented on database ?

To shrink Log file you have to run following command.
DBCC SHRINKFILE (  ‘Database_log’ , NOTRUNCATE)
So here we used  NOTRUNCATE option because in log shipping  transaction log  sequence important if  you run the normal  Shrink file or with truncate file option then log shipping will be failed.
So run Shrink File with NOTRUNCATE option. Although many DBA & Sql Server experts   gave suggestion to avoid shrink Log file.
But we can do shrink file in log shipping with NOTRUNCATE option if database Log size too much large and you have space issue.

Thanks

Rajat