This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.
Unzip GZ files using Powershell
Hello
I have Windows 2008 Server with some GZ type files in a folder. I would like to script unzipping them using Powershell, can someone tell me if this is possible and how I would do it?
The folder is d:\data_files\ and I'd like to uncompress all the .gz files in there.
I have Windows 2008 Server with some GZ type files in a folder. I would like to script unzipping them using Powershell, can someone tell me if this is possible and how I would do it?
The folder is d:\data_files\ and I'd like to uncompress all the .gz files in there.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
You can use powershell to call the CLI of any decompressoin program. I use powershell to run 7zip all the time.
Thanks I hada look at 7zip
I see the command line stuff here: http://www.dotnetperls.com/7-zip-examples which talks about using the "e" command
What I'm not sure is how I'd call the CLI of 7zip in Powershell, get it to unzip those files, and then let the Powershell script do some other stuff with these unzipped files ?
I see the command line stuff here: http://www.dotnetperls.com/7-zip-examples which talks about using the "e" command
What I'm not sure is how I'd call the CLI of 7zip in Powershell, get it to unzip those files, and then let the Powershell script do some other stuff with these unzipped files ?
It is as simple as this:
$folder = 'd:\data_files\'
$7za = 'C:\Program Files\7zip\7za.exe'
get-childitem $folder -filter *.gz |
foreach-object { & $7za e $_.FullName $folder }
So this seems to work:
$folder = 'd:\data_files\'
$7za = 'C:\Program Files\7zip\7za.exe'
get-childitem $folder -filter *.gz |
foreach-object { & $7za e $folder }
But what happens is that it extracts the files to the folder I'm running the script from. I need the files to be extracted to $folder as well.
I tried
$folder = 'd:\data_files\'
$7za = 'C:\Program Files\7zip\7za.exe'
get-childitem $folder -filter *.gz |
foreach-object { & $7za e $folder -o$folder }
But what it does is create a folder named $folder to extract the files to! :-)
Any ideas guys?
$folder = 'd:\data_files\'
$7za = 'C:\Program Files\7zip\7za.exe'
get-childitem $folder -filter *.gz |
foreach-object { & $7za e $folder }
But what happens is that it extracts the files to the folder I'm running the script from. I need the files to be extracted to $folder as well.
I tried
$folder = 'd:\data_files\'
$7za = 'C:\Program Files\7zip\7za.exe'
get-childitem $folder -filter *.gz |
foreach-object { & $7za e $folder -o$folder }
But what it does is create a folder named $folder to extract the files to! :-)
Any ideas guys?
-o$folder should work, but does not. Anyway, you need to provide a single archive with the syntax shown above, or a path including a file mask; that is why I used $_:
$folder = 'd:\data_files\'
$7za = 'C:\Program Files\7zip\7za.exe'
get-childitem $folder -filter *.gz |
foreach-object { & $7za e $_.FullName "-o$folder" }
$folder = 'd:\data_files'
$7za = 'C:\Program Files\7zip\7za.exe'
& $7za e $folder\*.gz "-o$folder"
Perfect, I used the latter which works exactly as I wanted it! :-)
Could you explain what you changed? Also, what does the & character mean and do?
Could you explain what you changed? Also, what does the & character mean and do?
Because of the semantical parsing PowerShell applies, a dollar is sometimes not taken as the variable prefix, but instead literally. That is what happens if you just use -o$folder. Putting a string into double quotes switches into a different parsing mode, which tries harder to find a variabe reference. Would the parameter allow for -o $folder, which it does not, no issue had arised, as this is treated correctly by PS.
The ampersand operator is used for interpreting the next string as a command. Just using a variable reference as first token on a commandline does not work, PS is in "expression mode" when it sees that, and will treat the var content just as a string instead of a command. But it would not help if we used the path directly, it contains spaces, so would need some sort of escaping, which is usually done by ticks or quotes - and the same issue would arise, a string as first token will not be used as command. Or in short:
& "C:\path to some exe\This is the.Exe"
runs the command,
"C:\path to some exe\This is the.Exe"
just results in the string.
If you put the command into PATH, and the command does not contain special characters like spaces, you could of course just call it:
7za e $folder\*.gz "-o$folder"
but not
C:\Program Files\7-zip\7za.exe e $folder\*.gz "-o$folder"
The ampersand operator is used for interpreting the next string as a command. Just using a variable reference as first token on a commandline does not work, PS is in "expression mode" when it sees that, and will treat the var content just as a string instead of a command. But it would not help if we used the path directly, it contains spaces, so would need some sort of escaping, which is usually done by ticks or quotes - and the same issue would arise, a string as first token will not be used as command. Or in short:
& "C:\path to some exe\This is the.Exe"
runs the command,
"C:\path to some exe\This is the.Exe"
just results in the string.
If you put the command into PATH, and the command does not contain special characters like spaces, you could of course just call it:
7za e $folder\*.gz "-o$folder"
but not
C:\Program Files\7-zip\7za.exe e $folder\*.gz "-o$folder"
Premium Content
You need an Expert Office subscription to comment.Start Free Trial