I plan to buy 2 licenses of your product this month.  I have tested and proven the database speed of your product for backup/restore.  I am interested in the Log Shipping features.  Is there any Stored Procedure or mechanism to make the failover automatic between the 2 servers linked via Log Shipping?  Any advice on this?  Thanks.
      
      
      
      
      Comments
2 comments
- 
                
                   You would need to set up the failover mechanism on your servers manually, as SQL Backup does not perform the failover automatically. You would need to set up the failover mechanism on your servers manually, as SQL Backup does not perform the failover automatically.
 I would suggest googling for 'log shipping failover' to consider the various issues before deciding on a manual or automatic failover.
- 
                
                   At the simplest, you bring the database up using a RESTORE DATABASE [x] WITH RECOVERY and re-associate any SQL users in the database by creating a corresponding logon and running exec sp_change_users_login against each login, to associate the database user with the new SID. At the simplest, you bring the database up using a RESTORE DATABASE [x] WITH RECOVERY and re-associate any SQL users in the database by creating a corresponding logon and running exec sp_change_users_login against each login, to associate the database user with the new SID.
 But I agree the best thing to do would be to research all of the possible ramifications ging up the database in your particular circumstances.
Add comment
Please sign in to leave a comment.