What's the error you're getting?

Look up the powershell commands get-childitem and remove-item, and you should be well on your way.

You may even find a script to do what you want.

Get back to us if...

In your stored proc, why not simply check for rows which will cause an error (datalength > 2, in this case) , select them and return a message to the...

Some definitions appear to be in order:

machine = the physical / virtual server on which an instance of SQL Server is installed.

SQL Server = software that runs on a machine....

A web search using the words "Services Powershell Status" leads to the following:

get-service -name "MSSQLServer" -Computername TargetServerName

Which returns

Status Name ...

I know. It was frustrating, since we had to schedule our AD changes around the 15 minute nightly window for re-booting. Even more frustrating as it was only the primary...

Had a similar problem some months ago with renamed Windows accounts.

http://www.sqlservercentral.com/Forums/Topic1328455-1550-3.aspx#bm1352733

After banging our heads against the proverbial wall for a week, we stumbled upon the solution: re-boot the SQL...

@gary: +1

Jeff,

A while back I experimented with TVPs and Powershell.

Basically, you create a table on a SQL server, and create a stored proc with a TVP to handle the inserts.

In...

Wow, good to know.

It appears you can use an ip address, perhaps that will allow you to move forward while they debate changes to the naming convention.

Try with square brackets? [server-name]?

As a DBA and occasional AD admin, Powershell considerably simplifies my life.

Goodbye .bat, see ya later mmc AD. SQL OLE Automation was, IMHO, nearly unusable.

I do have the luxury of...

Same here. I had a quick look at Tableau BOL, I must say, it seems a little obscure to me. Or maybe I also need more coffee.

Sure you can: My AD account does not have a Windows SQL Login, but I am a member of a group that does.

SELECT SUSER_NAME(); returns me (not the group).

go

-- ...

It is possible, if the login you're using has the correct permissions. See EXECUTE AS in BOL.