Tom, Thank you for the explanation. I have one additional folllowup question. When the database was created backups were configured using a maintenance plan and done once a day. This once...

I am curious as to why the recommendation to not shrink the log file. I am in a similar situation, I have a databse which is about 4GB and the...

Thank you for the suggestions. I will check into this.

In the Query Analyzer I execute the following query against each server...

select suser_sid('user')

and a different value is returned for each sid so I guess that means they are different. Does...

Thanks for the response but this raises a couple of additional questions. If I backup the primary and restore it to the secondary what would I gain by running the...

I had two difficulties, the first being the 14261 error. The workaround for this is to be found in KB article 298743 BUG: All Changes May Not Be Rolled Back...

Thank you for the update. I guess my question is whether or not Microsoft has a recommendation for this setup and if there are any pieces of standby databases which...

I figured out my problem. I did not check the Log Users Off Server box when setting up the maintenance plan. Checking that seems to have resolved the issue.

I spoke with the users and am assured that the application, delivered by a third party, requires this functionality. I resolved the problem by creating a proxy account.

My next question...

Thanks for the responses. I resolved the problem. I stopped the SQLSERVERAGENT service nad then, in the Enterprise Manager chose the SQL Server, right clicked and asked it to connect...

Greetings, I have tried that and I receive the message indicating the database is in single user mode and only one login is permitted. I don't understand why it thinks...

Yes I have and it returns the same error. I don't understand it. Are there some permissions I need to set on the sa user in order to do this?

Greetings, I restarted both the MSSQLSERVER and SQLSERVERAGENT services. I then bring up the Enterprise Manager and attempted the restore again with the same message displayed. I did not click...

The problem is resolved. I had upgraded the standby server from standard to enterprise edition and it turns out when that is done some log_ship* tables are not created. See...

I found the answer. Thanks.