george sibbald (5/3/2009)

---

cmille19 (7/20/2007)

---

That's correct at the DR site there is an identical server where all volumes are replicated at the disk level from one SAN to another SAN over...

Created a Powershell script to import Excel 2007 or 2003 to a SQL table, Import-ExcelToSQL

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...

jsimpson (3/12/2009)

---

Great stuff. I have no problems at all with get-sqldata, but I cant get set-sqldata to work...

Ok, so this works

Get-SqlData 'VISTA-LAPPY\SQLEXPRESS' Worldship 'SELECT top 3 *...

Are you passing the SQL instances as a parameter? For example, like this:

./get-invalidlogins 'Z002\SQL2K8'

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...

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"...

Phil Factor (1/2/2009)

---

Is the SMO library freely-distributable? What would happen if you created a Powershell application using SMO, and then wanted to install it on a computer that didn't have...

David,

Try executing just ./diskusage.ps1 by itself and see if...

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...

Are CSV files on the local SQL Server? Is the SQL Agent running under Local System or a Windows account?

valenzat (12/8/2008)

---

Thank you for your reply cmille19, the job works fine for generating the csvs but after running run-smo step im getting this:

The step did not generate any output. ...

There are huge differences in licensing terms for virtualized SQL Server vs. Oracle and yes Microsoft is more virtualization friendly from a licensing perspective. Here's a link to an article...

I have dozens SQL Agent jobs in 2000 and 2005 servers which call powerhell scripts from powershell.exe. The JobStep type is set to CmdExec. Try testing a single job step:

C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.EXE...

Its kind of funny to see a white paper touting running Oracle virtualized when unliked SQL Server, Oracle is not virtualization friendly from a licensing perspective. Oracle requires you license...