StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19623134
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-10-27T20:27:59.483
FavoriteCount
0
LastActivityDate
2013-10-27T20:27:59.483
LastEditDate
LastEditorUserId
0
OwnerUserId
2901928
ParentId
19611927
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
WMI can be a pain to configure, especially if you're on a secure network. Here's <a href="http://msdn.microsoft.com/en-us/library/aa389290%28v=vs.85%29.aspx" rel="nofollow">some guidance</a> if you want to go down that route. You didn't say what OS's you have at each end. If you're on 2008 R2 or later, you already have PowerShell 2.0. If you can install 3.0 or 4.0, you'll get a better experience (easier to <a href="http://technet.microsoft.com/en-us/library/hh849694.aspx" rel="nofollow">set up remoting</a>, auto-loading of modules, for example). As long as you're on PowerShell 2.0, you should take a look at PowerShell remoting. Fire up powershell and run: <pre><code>help about_remoting </code></pre> From there, you'll be lead to: <ul> <li>about_PSSessions </li> <li>about_Remote_Disconnected_Sessions</li> <li>about_Remote_Requirements</li> <li>about_Remote_FAQ</li> <li>about_Remote_TroubleShooting</li> <li>about_Remote_Variables</li> </ul> There's quite a bit of reading to do and I can't possibly do it justice here but to whet your appetite, once remoting is configured, you can issue this on the source machine: <pre><code>Invoke-Command -ComputerName server1 -ScriptBlock { Get-ChildItem C:\ } </code></pre> to get the contents of server1's C:. You're not limited to running PowerShell commands. For example, <pre><code>Invoke-Command -ComputerName server1 -ScriptBlock { ipconfig /all } </code></pre> will bring back the detailed ipconfig from server1. You can establish sessions and run multiple commands using variables (local and remote). You can, if you want, also use WMI but using the new CIM cmdlets which run over WinRM - the same technology used by PowerShell remoting - rather than evil DCOM. Try <code>Get-Command *cim*</code> to get a list and then use 'help' to get more info. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POShut down application remotely before database refresh
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USSimon
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COThanks for this, good feedback! I'm going to spend time first working with Powershell and see where it takes me.
 singulars
 PostPostId
 PO
 UserUserId
 USuser1133448

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.