fuzzyocelot
Programmer
I need to automate the weekly load of two files from an internal ftp site into one of the databases on our SQL 2000 cluster (SP3a). Normally we do this manually every week. However, it needs to be automated to run after hours because people are starting to use this database during business hours. I can’t update the tables while they’re using them because the process truncates the tables and then loads the data.
The problem is the files are unix compressed files (i.e. file.unl.Z) and I need to be able to unzip them on the Windows server (Win 2003 SP2). I've tried using the compact command via the command prompt and it doesn't work. Probably because it's a unix compressed file. Normally I use the evaluation version of WinZip to unzip the files onto my desktop and then I run the DTS package to load the files. It's my understanding that WinZip is no longer supported by our organization and chances are slim I’ll be allowed to download/buy a third party program. I may be able to as a last resort if I’ve exhausted all other options. Does anyone know of any tool or command that will allow me to uncompress these files on a Windows server via the command line? I can't find any such tool within SQL 2000 or 2005.
I appreciate any advice!
The problem is the files are unix compressed files (i.e. file.unl.Z) and I need to be able to unzip them on the Windows server (Win 2003 SP2). I've tried using the compact command via the command prompt and it doesn't work. Probably because it's a unix compressed file. Normally I use the evaluation version of WinZip to unzip the files onto my desktop and then I run the DTS package to load the files. It's my understanding that WinZip is no longer supported by our organization and chances are slim I’ll be allowed to download/buy a third party program. I may be able to as a last resort if I’ve exhausted all other options. Does anyone know of any tool or command that will allow me to uncompress these files on a Windows server via the command line? I can't find any such tool within SQL 2000 or 2005.
I appreciate any advice!