I have a VBScript that works fine in standalone mode (It copies Trans logs dumps between SQL servers). Under SQL 2K I created a job and tried to import this script into a job step. When I do so I get the error:
The specified file (…) is 3446 characters in size, which is larger than the available free space in the current job step command (3200 characters). Do you want to continue opening this file but have its contents truncated?”
1. Can I increase the available “free space”>
2. I haven’t tested it but I wonder if the Job step could call “myCopy.bat” which then will call the full VBScript?
TIA,
Bill