Linked SQL server showing strange behavior

Results 1 to 2 of 2

Thread: Linked SQL server showing strange behavior

  1. #1
    Join Date
    Dec 1969

    Default Linked SQL server showing strange behavior

    I have two SQL Server Instances on two servers. One server is my webserver and database server and the other one is just a database server. i have an application that calls a stored procedure located on the webserver/database server that runs a query on the OTHER database server. I use linked tables in my first instance to make the call possible. <BR><BR>Everything was working just fine for months until the database server was restarted and the IP address was changed. The name of the database is the same however and my first SQL Server instance has no problems running queries on the other databases tables. However, when you try to run the application i get the following error:<BR><BR>Login failed for user &#039;sa&#039;. Reason: Not associated with a trusted SQL Server connection<BR><BR>I have mixed mode authentication selected and my security uses the security context with username=sa and password=sa.<BR><BR>So here&#039;s the weird part. <BR><BR>The application will only run correctly when i manually run a SQL command from my webserver&#039;s SQL Analyzer on the linked SQL Server. however, after a few minutes, the same error comes back!! so as a temporary fix, i scheduled a dts job to run a simple query on the linked server every two minutes, so the application keeps working! It&#039;s almost as if the webserver&#039;s sql server forgot that the linked server is there, and by running a simple query in query analyer, the connection gets refreshed and everythings normal again - for about 3 minutes!<BR><BR>I am completely stumped by whats happeneing and appreciate any help. Thank you.

  2. #2
    Join Date
    Dec 1969

    Default RE: Linked SQL server showing strange behavior

    That&#039;s truly bizzare. Are you connecting via TCP/IP, or Named Pipes? The only lousy explaination I could think of (and I have *no* good explainations) would be that maybe, over named pipes, the network loses the connection at some point? <BR><BR>That&#039;s not the error I would expect from that senario though.<BR><BR>My *best* suggestion would be to try pinging one of the SQL Server-centric forums...Either or or the MS SQL Server newsgroups and see if any of the DBAs hanging out there have any ideas.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts