|
|
Posted by Ed Murphy on 10/05/06 17:39
One of my clients has a stored procedure on their secondary server that
copies a bunch of data from the production server. (Replication will
break the accounting software, according to its authors. The production
server generates a nightly full backup, so if the secondary can be
scripted to do a nightly restore from that same file, then that would
probably be a Big Win.)
Anyway, if I execute the stored procedure from Query Analyzer, it
finishes (after nearly 24 hours) - tested once recently, and I'm sure
at least a few times at some point in the past. If I run a SQL Server
Agent job that executes the stored procedure, then it gets cut off after
about 15-20 minutes - tested once recently with a manual run, and for
several weeks of scheduled runs before that. (This being a secondary
server, it took a while for the problem to be noticed.) What are the
likely causes of this?
Both servers are running SQL 2K with SP3, and limited to TCP/IP and
named pipes. RPC is allowed, with a 600-second timeout, but that
doesn't seem relevant, since both the successful and unsuccessful
methods go well past that length. The production server is a recent
purchase, and works well for their daily operations; the secondary
server and/or its network connection might be flaky for all I know,
but that doesn't seem relevant either, since success appears to
depend consistently on method of execution.
Navigation:
[Reply to this message]
|