Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Linked Server – How to Determine if Anyone is Using It?

Status
Not open for further replies.

fuzzyocelot

Programmer
Jul 22, 2003
333
US
Hi to all!

We have a linked server defined within a SQL 2000 server. The remote server is a SQL 2005 server. I don't think the link is being used. How can I find out if anyone is using it? I want to delete it if it's not being used.

Here's the main situation:

Our main SQL database development server went down the other day. One group of people whose application is connected to the production server said they lost their connection when the development server went down. They also said their connection came back up when the development server came back up. I'm hoping this is just a coincidence. The application is web-based. The developer says the DSN connection string is showing a connection to the database on the production server only. She says it's not connected to the development server. I looked through their database on the production server. I don't see any place where it could be connecting to the development server. There are only 2 stored procedures - one for truncating tables and one for loading data from other tables. The development server name is no where in these procedures.

I have a SQL trace running on the development server to see if there is any activity over there. So far there is none.

No one else reported a connection problem to the production database server during this time. Hundreds of people use this production server. If they lost their connection, we would have definitely heard about it because the development server was down all morning.

Does anyone have any ideas or know how I can determine if anyone is using this linked server? It's in SQL Server 2000.

Thanks!
 
here is my recommandation.

You can make linked server to user some designated login that only you know.

Then go to server where linked server connects to, turn the security audit login to log both failure and success login attempt.

Later on check out event viewer for login history for the sql server
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top