|
|
|
SSC Veteran
 
Group: General Forum Members
Last Login: Today @ 8:14 PM
Points: 232,
Visits: 499
|
|
|
|
|
|
SSC-Enthusiastic
Group: General Forum Members
Last Login: Saturday, October 17, 2009 2:00 PM
Points: 109,
Visits: 43
|
|
That's a good article, except for a couple of things.
Why do people still literally use commas as field separators (unless they have to, because the tool/function/utility doesn't support anything else)? Gaaaahhh! The example even uses the field separator parameter...
And, well, it's PowerShell. I'd rather do this stuff in INTERCAL, but to each their own...
Of course, BCP does this stuff as well...
|
|
|
|
|
SSC Eights!
Group: General Forum Members
Last Login: Today @ 2:15 PM
Points: 852,
Visits: 2,369
|
|
corey lawson (12/15/2008)
That's a good article, except for a couple of things.
Why do people still literally use commas as field separators (unless they have to, because the tool/function/utility doesn't support anything else)? Gaaaahhh! The example even uses the field separator parameter...
And, well, it's PowerShell. I'd rather do this stuff in INTERCAL, but to each their own...
Of course, BCP does this stuff as well...In search of enlightenment, what should we be using as field separators?
---------------------------------------------------------
For Best Practices on posting questions that get answered quickly, see http://www.sqlservercentral.com/articles/Best+Practices/61537/
and
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
|
|
|
|
|
Hall of Fame
Group: General Forum Members
Last Login: Thursday, November 12, 2009 7:14 AM
Points: 3,295,
Visits: 964
|
|
|
|
|
|
Grasshopper
Group: General Forum Members
Last Login: Friday, October 23, 2009 5:50 AM
Points: 20,
Visits: 64
|
|
I have found that TAB separated files seem to cause the least number of problems. Unfortunately TABs aren't always possible, if you have to work with a file created by a mainframe or a file that you receive by FTP then TABs probably aren't an option.
It is possible to Bulk Insert a file starting at the "nth" row without creating a format file. Simply use the firstrow option.
Bulk Insert #temp
From 'c:\data.txt'
With (firstrow = 2)
|
|
|
|
|
SSC Veteran
Group: General Forum Members
Last Login: Today @ 8:14 PM
Points: 232,
Visits: 499
|
|
thermanson (12/16/2008)
I have found that TAB seperated files seem to cause the least number of problems. Unfortunately TABs aren't always possible, if you have to work with a file created by a mainframe or a file that you receive by FTP then TABs probably aren't an option.
It is possible to Bulk Insert a file starting at the "nth" row with out creating a format file. Simply use the firstrow option.
Bulk Insert #temp
From 'c:\data.txt'
With (firstrow = 2)
Thanks for the tip about about firstrow. Unfortunatley the built in Powershell cmdlet, Export-CSV only supports a comma as a separator.
|
|
|
|
|
Forum Newbie
Group: General Forum Members
Last Login: Monday, November 16, 2009 3:32 PM
Points: 8,
Visits: 156
|
|
when i ran:
./diskusage.ps1 sydw1255|export-CSV -path ./diskusage.csv -noTypeInformat
I get this error:
An empty pipe element is not permitted.
At F:\Working Folders\PowerShell\diskusage.ps1:4 char:2
|
|
|
|
|
SSC Veteran
Group: General Forum Members
Last Login: Today @ 8:14 PM
Points: 232,
Visits: 499
|
|
David Ly (12/16/2008)
when i ran:
./diskusage.ps1 sydw1255|export-CSV -path ./diskusage.csv -noTypeInformat
I get this error:
An empty pipe element is not permitted.
At F:\Working Folders\PowerShell\diskusage.ps1:4 char:2
David,
Try executing just ./diskusage.ps1 by itself and see if you get any output then add space pipe space export-csv -path ./diskusage.csv -noTypeInformat as shown in the article.
Verify your execution policy in Powershell also by running get-executionpolicy. Set your policy to remotesigned by running set-executionpolicy remotesigned if it is not already.
|
|
|
|
|
Forum Newbie
Group: General Forum Members
Last Login: Monday, April 27, 2009 2:15 AM
Points: 6,
Visits: 21
|
|
David Ly (12/16/2008)
when i ran:
./diskusage.ps1 sydw1255|export-CSV -path ./diskusage.csv -noTypeInformat
I get this error:
An empty pipe element is not permitted.
At F:\Working Folders\PowerShell\diskusage.ps1:4 char:2
I get the same error - I believe it's due to the the following pipe (bold)?
Get-WmiObject -computername "$ComputerName" Win32_LogicalDisk -filter "DriveType=3"
|
foreach { add-member -in $_ -membertype noteproperty UsageDT $((Get-Date).ToString("yyyy-MM-dd"))
I can't use Get-DiskUsage.ps1 if I run it on it's own. Any help appreciated. I would really like to get this working. I'm hoping to use it for all manner of wmi queries so I can store them in a db. However I haven't managed to get any of the examples listed working at all.
Cheers
|
|
|
|
|
SSC Veteran
Group: General Forum Members
Last Login: Today @ 8:14 PM
Points: 232,
Visits: 499
|
|
There are some extra returns in the code in the article. Try this instead (notice the line breaks are different):
param ( [string]$ComputerName = "." )
Get-WmiObject -computername "$ComputerName" Win32_LogicalDisk -filter "DriveType=3" |
foreach { add-member -in $_ -membertype noteproperty UsageDT $((Get-Date).ToString("yyyy-MM-dd"))
add-member -in $_ -membertype noteproperty SizeGB $([math]::round(($_.Size/1GB),2))
add-member -in $_ -membertype noteproperty FreeGB $([math]::round(($_.FreeSpace/1GB),2))
add-member -in $_ -membertype noteproperty PercentFree $([math]::round((([float]$_.FreeSpace/[float]$_.Size) * 100),2)) -passThru } |
Select UsageDT, SystemName, DeviceID, VolumeName, SizeGB, FreeGB, PercentFree
|
|
|
|
