Unix Technical Forum

SQL server 2000

This is a discussion on SQL server 2000 within the SQL Server forums, part of the Microsoft SQL Server category; --> osql command is not executing on Remote server(by using link server) osql -S ucmain -U sa -P abc -l ...


Go Back   Unix Technical Forum > Database Server Software > Microsoft SQL Server > SQL Server

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 03-01-2008, 02:54 PM
ahsan kabir
 
Posts: n/a
Default SQL server 2000

osql command is not executing on Remote server(by using link server)
osql -S ucmain -U sa -P abc -l 2 -Q

ucmain is remote
abc password

After executing the above command I got time out expire messsage
What is the reason ?
It is noted that 35 server is connected with the gateway where the osql
command is executing. when I want to execute the command only 2 server
shows time out message but all other going fine.


*** Sent via Developersdex http://www.developersdex.com ***
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 03-01-2008, 02:54 PM
Erland Sommarskog
 
Posts: n/a
Default Re: SQL server 2000

ahsan kabir (ahsan_kabir@rediffmail.com) writes:
> osql command is not executing on Remote server(by using link server)
> osql -S ucmain -U sa -P abc -l 2 -Q
>
> ucmain is remote
> abc password
>
> After executing the above command I got time out expire messsage
> What is the reason ?
> It is noted that 35 server is connected with the gateway where the osql
> command is executing. when I want to execute the command only 2 server
> shows time out message but all other going fine.


This is probably a problem with your network. I was faced with the same
mystery today. I was connected to a server in Query Analyzer, and I was
able to run queries against it. But for some five minutes I was not able
to connect to the server through an application or through OSQL. I had
the same problem yesterday.

One thing I tried was to ping the target server. What I noticed was
that the lines in the output came several seconds apart, despite the
response time being listed as < 1 ms. I also noticed that TTL (Time to
Live) was as low as 125.

Note that when OSQL cannot reach the server at all, the error message
is different. When you get "timeout expired", I assume that OSQL is
able to get a connection to the server, but ia nor able to fully
open it in due time.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 01:02 PM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.2.0
www.UnixAdminTalk.com