|
|
Posted by Erland Sommarskog on 10/01/16 11:42
pb648174 (google@webpaul.net) writes:
> osql -b -n -E -S ServerName -i Backup.sql
>
>
> We use a single backup server that not only connects to all the various
> databases and backs them up, but also copies the .bak files to another
> drive, copies application files to a backup area, zips them up, etc.
>
> I think this is related to another issue I see on some client's servers
> where the web server intermittently cannot talk to the SQL server..
> This error also happens intermittently. I have never figured out what
> the issue is so I ping the newgroup every now and then hoping someone
> will have seen it themselves. My guess is that it is network related.
If the error message is exactly "Timeout expired" and nothing else to
go with it, it looks very much like a query timeout. But should not get
one with that command line, unless there is some undocumented environment
variable that affects the query timeout.
Do you have any idea how time it take before the timeout elapses?
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|