First thing.. running SQL Agent service with sa account is not a good practice.

Also this error is not SQL agent error. It is from some application trying to access the...

Strange things are going on with your DB. Are your jobs have an end date specified?

Have to changed the date back to original?

Are there anything in SQL Server/ Agent error...

I would suggest to use Roles in the Database and create a Role for reporting purpose and deny that role access to OLTP DB.

Otherwise you can create a trigger on...

Some time around year 2000.

Which replication topology you are using?

Read through this. Very nice article by Gail Shaw.

https://www.simple-talk.com/sql/database-administration/gail-shaws-sql-server-howlers/

I believe yes you can do this.

When you are configuring your publication, do not initialize from backup.

Setup all your publication in this way and populate data in subscriber manually.

The...

I would suggest you to read through this.

https://www.simple-talk.com/sql/performance/sql-server-statistics-questions-we-were-too-shy-to-ask/

CTRL+M

Get the value of room# in a variable based on the PK of the table. Compare that with the Vale passed the SP and then write your logic based on...

You are always welcome.

Looking at your steps seems alright to me and as you said everything has been configured correctly. So if you see any error on the error logs...

Yes. That was what I was doing. But I wanted the fail-over to be seamless. Without getting me involved at any time.

I think I am missing something. When you restore DB in mirror, you do that with recovery switch enable. SO it will always be in restoring mode.

I have never tried that but first prerequisite for that as per MS :-

"For a mirroring session to be established, the partners and the witness, if any, must be running...

To achieve replication with mirroring you should use remote shared distributor and configure Principle & Mirror as Publisher on that distributor.

Also use that Distributor on both Principle & Mirror.

Here...