jschaddock
Programmer
Hello,
I am currently working migrating an application from SQL 7 to 2000. I'm testing out a scheduled job which imports a file using BCP. The original job on the current SQL 7 Server runs a step that uses an operating system command of:
bcp new_reference_data_test..exchange_rates in etc...
however, when running this on our new SQL 2000 server it does not work. I know that there are no problems with the code as it works when running the step as a Transact-SQL script inside xp_cmdshell.
I'm looking at the configuration of the SQL 2000 server trying to figure out why I can't run this code as an operating system command but so far I can't spot anything. Can anyone help? Is there a system stored procedure or option to allow operating system commands in SQL that I am missing?
Thanks
J
I am currently working migrating an application from SQL 7 to 2000. I'm testing out a scheduled job which imports a file using BCP. The original job on the current SQL 7 Server runs a step that uses an operating system command of:
bcp new_reference_data_test..exchange_rates in etc...
however, when running this on our new SQL 2000 server it does not work. I know that there are no problems with the code as it works when running the step as a Transact-SQL script inside xp_cmdshell.
I'm looking at the configuration of the SQL 2000 server trying to figure out why I can't run this code as an operating system command but so far I can't spot anything. Can anyone help? Is there a system stored procedure or option to allow operating system commands in SQL that I am missing?
Thanks
J