|
|
Posted by Erland Sommarskog on 10/01/29 11:42
pb648174 (google@webpaul.net) writes:
> After executing osql from the command line via the Windows scheduled
> task interface, the following error is returned: "Timeout expired"
>
> The code in the sql is as follows:
>
> BACKUP Database DBName to DISK='D:\Files\Backups\DBName.bak' WITH INIT
> go
>
> Is the timeout happening during the backup or in just connecting to the
> server? There is no firewall between the two machines they are on the
> same hub, and the machine executing osql has SQL 2000 installed while
> the database machine has SQL 2005.
Exactly how the command line for OSQL look like?
It sounds like it includes the -t option, which specifies a maximum
execution time for queries. By the default, OSQL does not time out,
which is why suspect that -t is there.
Notice that this timeout is a client-side thing. What happens when the
timeout elapses is that that the client cancels the query.
By the way, why don't you run backups from SQL Server Agent?
--
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]
|