Log shipping - Destination server problem

[Mich]

This is my first time setting up log shipping so please bear with me.

I've created the db on the primary server that I want to back up. It's set to FULL recovery mode. The db does not exist on the secondary server. I go through the Maintenance wizard and every thing seems perfect until I get to the 'Specify the Log Shipping Destinations' screen. From everything I've read, at this point I'm supposed to point the log shipping to my secondary server. The problem is when I attempt to add a destination my only server choice in the Add Destination Database screen is my primary server. I do not see the secondary nor can I manually change it to the secondary (not that I know of).

Any ideas?

-If it ain't broke, break it and make it better.

 

[Mich]

I figured out my problem. BOTH servers in the log shipping process must have Enterprise edition installed. The vendor I'm working with said only the primary would need it. Once I installed Enterprise edition on the secondary server everything ran fine.

Another question though, how do I swap to my secondary server should my primary fail? My main area of concern is the db rights. When setting up log shipping the databases are created in one of two modes - Read only and no access. I set up my job as read only. In testing the log shipping I wanted to make sure, should the primary fail, I can easily switch over to the secondary, but I cannot change the attribute on the backup databases. How can I point my application at the secondary server and be functional within minutes?

-If it ain't broke, break it and make it better.

 

[Mich]

Nevermind, I would restore the last translog available and include WITH RECOVERY.

-If it ain't broke, break it and make it better.