Re: OSQL Batch File Problem
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Tue, 22 Aug 2006 06:53:26 -0600
Try fully using fully qualified path for the input file -
C:\SomeFolder\mysqlscript.sql
or whatever the path is.
-Sue
..
On Tue, 22 Aug 2006 05:26:01 -0700, J. Baez
<JBaez@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I have a scheduled task that runs a batch file in windows 2003 server which
is running SQL Server 2000 Enterprise.
The batch file contains the line:
OSQL -i myscript.sql -Umyuser -Pmypassword -Slocalhost -o mytrans.log
the 'myscript.sql' file updates a table with another table of the exact
number of rows.
When the scheduled task runs, the 'mytrans.log' file shows 0 rows were
affected.
If I run this myself from the command line, 22,000 rows are affected which
is correct.
I am guessing there is some sort of permission/authentication issue here. I
am sending the right username/password for SQL and for windows to run the
task.
Any idea what I could do to fix this?
Thanks,
J. Baez
.
- Prev by Date: Re: SQL 2005: WITH ENCRYPTION: Obfuscation revealed?
- Next by Date: Re: SQL 2000 Windows Authentication - Same User Multiple Groups
- Previous by thread: BOL ERROR: ALTER CERTIFICATE/ALTER ASYMMETRIC KEY
- Next by thread: Re: OSQL Batch File Problem
- Index(es):