How to monitor SQL Server connection quality?

Hello,
Are there any tools to monitor connection to SQL Server?

Occasionally I get error "The  database engine could not find the object 'TableName'. Make sure the object exists and that you spell its name and the path name correctly. If 'TableName' is not a local object, check your network connection or contact the server administrator"

Just wondering if the connection may interrupt, and if yes, is there any tool to indicate such interruptions?
Thank you
ForresterCAAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Vitor MontalvãoMSSQL Senior EngineerCommented:
I don't think that error is related to a connection. Connection errors have very explicit message.
If you are working with temporary tables check if there is some issue with the process, like try to access a table that isn't created yet.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ForresterCAAuthor Commented:
Vitor,
no there are no temporary tables, and tables are accessible if trying to open them manually from database window (FE is MS Access 2010).
I thought there could be short interruptions in connectivity.

Anyway, do you know of any connection monitoring tools that can ensure quality of connection?
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
Connection losts should be registered in the Event log.
Again, connectivity losts doesn't generate object not found's message. Without seeing the code I can only make guesses.
0
ForresterCAAuthor Commented:
This answer was the closest one.

In my question I had to add, that we were using shared MS Access front-end, which executed tables re-linking procedure on start.
Thus when one user is logging in, other users may experience missing tables, because for some small period of time linked tables were killed and then linked again.
Now we are executing  re-linking only once when updating FE, and error is gone.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.