Step 3 is for principle. You can not run that on Mirror since it is in restoring mode.

Please find attached the step by step script to reproduce the issue. What I realized that unless you explicitly specify DEFAULT_DATABASE=your Mirrored DB, it does not work.

So, if you have done that..post he create table & some sample data script..

When setting up Publication did you check the check box for "Create/ schedule the snapshot agent?" and then initialized from backup?

Thank you very much Lynn for asking me to write the step by step script for you to replicate issue on your side.

While I was doing that I just realized...

Yes, I add the user to 2 roles in mirror and it is high safety and failing over automatically.

Could you please post the detailed error message? Is this related to a network issue?

Thank Lynn,

At least you tried.

Lynn,

Please let me know what information you want. I will provide as much as information I could give.

It is standard mirroring set up with high safety.

All the Servers...

Yes, that's right and also using the same SID as of primary.

Anybody...Please..

Is there a backup file named "May10.bak" on C: drive? If yes, do you have/ account have enough privilege to access that file?

Also make sure that your analysis have not excluded Foreign keys. Because lot many scripts available online do not consider FK while doing unused Index analysis.

I do agree with...

What is the state of database in secondary server? If it is in Standby mode, have you checked the Checkbox "Disconnect uses in the databse when restoring backup"

Use sp_send_dbmail to construct desired subject lines and use that a part of job to send alerts.