If you are able to connect after restart, then mismatching SID's could be only thing which I can think of. We had same issue in our environment and after SID's...

Have you tried specifying the port # explicitly in the connection string?

"Server=xx.xx.xx.xx,port #"

Are the SID'd for the application user on primary & mirror server are same and also default DB for that user is set?

I would suggest to test this via failing...

I will try to explain.

Lets assume you have given write permission on subscriber and somebody deletes a row which is in publisher and later somebody updates that row in publisher...

I would recommend books online.

http://msdn.microsoft.com/en-us/library/ms187956.aspx

You can take a backup and restore it manually on DR site and choose option "Secondary database is already initialized."

Keep in mind that that you have to restore DB with...

Thank you very much for your response. I do agree with you that if we use Integrated security everything can be managed via AD but my SYS and Network admin...

Thank you very much for taking time to look into it and answer.

Yes I have looked into it and as I have told it doesn't give any explicit reason...

I would also suggest to check the power setting on new server.

As asked by Grant Could you please post the actual execution plan. That will help.

Meanwhile you can try removing the OR from Query and use Union All and see if...

It depends.

But the answer to other question is:-

Logical Read: Number of pages read from data cache.

Physical Read: Number of pages read from the disk.

CPU time refers to...

So that is a good news.

Follow the steps as suggested earlier ..

you can fail over to Mirror --> Configure Security and set the Witness Server and -->Fail back to...

Like this?

set lock_timeout 1000

declare @sql nvarchar(100)

set @sql = 'alter index PK_Users on users rebuild '

exec sp_executesql @sql

It is still working for me.

what about AND?

How you are trying to do it? I believe you are doing in the script where you have your index rebuild specified. In that case it should work.

I just...