|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, February 17, 2012 8:35 AM
Points: 6,
Visits: 22
|
|
Great thanks that works now - I'm having trouble getting sqlcmd to work correctly so I've started looking at BCP.exe
I've managed to rewrite your script so that my wmi results are output to a .xls file Does anyone know the BCP command to get a local xls file loaded into a remote sql table?
I can manage to get the command working if I copy the data out of the .xls and into a .txt:
db = TEST table = LogMemory server = lonwintel01
This bcp command works for .txt file - does anyone know the correct switches for a .xls file:
bcp TEST..LogMemory in "c:\ps\scripts\import.txt" -S lonwintel01 -T
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 5:46 AM
Points: 257,
Visits: 671
|
|
NevJam (1/14/2009) Great thanks that works now - I'm having trouble getting sqlcmd to work correctly so I've started looking at BCP.exe
I've managed to rewrite your script so that my wmi results are output to a .xls file Does anyone know the BCP command to get a local xls file loaded into a remote sql table?
I can manage to get the command working if I copy the data out of the .xls and into a .txt:
db = TEST table = LogMemory server = lonwintel01
This bcp command works for .txt file - does anyone know the correct switches for a .xls file:
bcp TEST..LogMemory in "c:\ps\scripts\import.txt" -S lonwintel01 -T
BCP does not work with Excel files. Keep in mind the T-SQL shown in the article for sqlcmd could have been executed with Query Analyzer, SSMS or osql instead of sqlcmd
BULK INSERT dbautility.dbo.DiskUsage FROM 'C:\Users\u00\bin\diskusage.csv' WITH (FIELDTERMINATOR = ',', ROWTERMINATOR = ''
You can use DTS or SSIS with Excel files.
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 5:46 AM
Points: 257,
Visits: 671
|
|
Blogged about Executing Powershell in SQL Server . Using the technique described in the blog post you have a fourth method to load Powershell data into SQL Server. The approach uses xp_cmdshell and XQUERY to return the result set.
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 5:46 AM
Points: 257,
Visits: 671
|
|
Created a Powershell script to import Excel 2007 or 2003 to a SQL table, Import-ExcelToSQL
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Sunday, February 17, 2013 2:38 AM
Points: 369,
Visits: 392
|
|
cmille19 (1/8/2009) 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
Thanks...though its so silly this article is still not updated, to get a 5 start rating known issue should have been fixed and a full set of files should have been attached for anyone to try quickly...
So i am able to export, lets see how does import do...
Prakash
Prakash Heda Lead DBA Team - www.sqlfeatures.com Video sessions on Performance Tuning and SQL 2012 HA
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Friday, May 10, 2013 11:16 AM
Points: 121,
Visits: 640
|
|
| Is there anyway to append the csv file instead of overwriting its contents?
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 5:46 AM
Points: 257,
Visits: 671
|
|
If you mean keep appending output to a CSV file, the export-csv cmdlet doesn't directly support this, however you could use the convertto-csv cmdlt and remove the header row as follows:
get-psdrive | export-csv ./psdrives.csv -NoTypeInformation get-psdrive | ConvertTo-Csv -NoTypeInformation | foreach {$start=$true} {if ($start) {$start=$false} else {$_}} | Out-File .\psdrives.csv -Append -Encoding ASCII
The code snippet above is based on a more complete solution described by Dmitry Sotnikov: [url=http://dmitrysotnikov.wordpress.com/2010/01/19/export-csv-append/][/url]
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Friday, May 10, 2013 11:16 AM
Points: 121,
Visits: 640
|
|
thanks for the reply. I'll take a look at that broader solution for that snippet. I actually got it working by saving my outgoing data into a variable, importing the contents of the csv file into another variable and appending the two together. My powershell scripting is quite novice so if you see any issues with this let me know :)
Here is the code I used:
$Temp = Get-SqlData $srcServer 'master' $qry $Last = import-csv "C:\filename.csv" $out = $Temp + $Last | export-csv -noTypeInformation -path "C:\filename.csv"
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Yesterday @ 7:56 AM
Points: 32,
Visits: 84
|
|
| @SSC Veteran : Thanks . Its working now by using the above commands
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Yesterday @ 9:57 PM
Points: 32,906,
Visits: 26,790
|
|
jcrawf02 (12/16/2008)
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?
How about it, Corey? What do you people should be using?
--Jeff Moden "RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."
For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
|
|
|
|