Use PowerShell to Administer SQL Server 2008

re: Use PowerShell to Administer SQL Server 2008

ScriptingGuy1 — Tue, 05 Oct 2010 16:00:52 GMT

We have changed that verbage to databases. Thanks for pointing it out.

re: Use PowerShell to Administer SQL Server 2008

Sean McCown — Tue, 05 Oct 2010 03:53:06 GMT

Justin,

Thanks for catching that mistake. You're right, I meant to say databases instead of servers there. We're changing it so it

should read correctly soon.

As to your other comment, you're right about the behavior of dir/gci, but you're mistaken about the fact that I left out the

context or just assumed the reader knew it. If you look in the text directly following the code, I very clearly state "First,

let us talk about how to get where you need to be. In the SQL Server Management Studio (SSMS), right-click the database folder

and click Start PowerShell in the shortcuts menu. Then type the code shown earlier."

So I don't believe I assumed anything. I gave the context of being in the databases folder.

Again though, thanks for taking the time to comment because if you missed that, then others may have too, and reading through

these comments may clarify this for someone.

Thanks,

Sean McCown

re: Use PowerShell to Administer SQL Server 2008

jrich — Mon, 04 Oct 2010 15:42:23 GMT

Nice post!

Just after your TSQL code you mistakenly said we'll be doing this for 200 servers, not databases. It could easily be done, but thats a different task!

Also one part you left out or assumed was the dir part. dir (or more so, gci) will only pull a list of databases if you are in the right location. you'll want to move to the correct location first.

The path looks something like this

sqlserver:\sql\<servername>\<instancename>\databases

If you navigate to that location your DIR will work as expected. you can do a DIR at any location you want, so for example, if you arent sure what instance to use, you can go to the server and do a dir to see what instances are available to you!

Justin