Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a client site that uses SQL Server. The site this morning was slow, and we realised that the primary database server was responsible for a lot of disk activity on tempdb (Server 2008, SQL Server 2008 R2, looking in the resource monitor), which was the reason for the slowness.

In the event log we saw this message every couple of seconds or so:

"Database Mirroring login attempt by user xxxxx failed with 'Connection handshake failed. The login xxxxx does not have connect permission on the endpoint. State 84"

The IT guys say these two things (tempdb being thrashed and a connection failure for the mirroring login) are unrelated - we're not so sure. Anybody say for definite?

P.S. we failed over the db server and the slowness went away, though the amount of disk IO on tempdb continues to rise, and the event log is still getting those error messages every couple of seconds


migration rejected from Oct 3 '13 at 21:56

This question came from our site for professional and enthusiast programmers. Votes, comments, and answers are locked due to the question being closed here, but it may be eligible for editing and reopening on the site where it originated.

closed as off-topic by Max Vernon, RolandoMySQLDBA, bluefeet, Paul White, Mark Storey-Smith Oct 3 '13 at 21:56

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Too localized - this could be because your code has a typo, basic error, or is not relevant to most of our audience. Consider revising your question so that it appeals to a broader audience. As it stands, the question is unlikely to help other users (regarding typo questions, see this meta question for background)." – Max Vernon, RolandoMySQLDBA, bluefeet, Paul White, Mark Storey-Smith
If this question can be reworded to fit the rules in the help center, please edit the question.

they are unrelated – Remus Rusanu Oct 24 '12 at 18:05
There should not be any relationship between the two, but it's worth eliminating that error anyway. Is mirroring meant to be setup between two servers? If not, disable the mirroring attempt on the remote server. If so then grant connection on that tcp endpoint to the login. – Nic Oct 24 '12 at 22:27
Sync or async mirroring? Which edition of SQL? – Jon Seigel Oct 25 '12 at 15:07

Those errors are totally unrelated. If you are getting errors with database mirroring being able to connect to an endpoint you need to look into your mirroring configuration and figure out what went wrong because something is very wrong.

As for tempdb thrashing that could be any number of things, but usually it's temp table usage, variable usage, or join memory spilling to disk.

I wish I could vote more than once. – user1240 Oct 25 '12 at 23:07