December 6, 2012 at 10:53 am
This may be a totally off the wall question, but it seems like it should be possible to do. Just can't find any specifics as to how I might accomplish it.
I have a situation in that I have the same database (structurally) across multiple SQL Server instances, with different database names. Through SSMS I have a local server group defined that references each unique instance and individual database. This allows me query each database at once with a single SQL statement, regardless of database name.
When queries are run through my SSMS environment, I have the option enabled to return the SQL Server instance in the grid output so the instance name is returned with each row. I would like to automate running my query and outputting the results to Excel via Powershell script.
What I'm hung up on is that I need to be able (with Powershell) to reference my SSMS local server group as the the data source that the query runs against, and run the query. Has anyone done this?
I appreciate any feedback..
December 7, 2012 at 9:02 am
Well, if you can get the information out of the file, registered servers are stored in
C:\Users\username\AppData\Roaming\Microsoft\Microsoft SQL Server\100\Tools\Shell\RegSrvr.xml
But I'd be much more tempted to set up my own text file or db table to store the server/database information.
Easy enough once you've got the list to run your query in a foreach loop.
December 24, 2012 at 1:34 pm
Have you heard of Central Management Server (CMS)? It supports the "interact with each server in a server group from PowerShell" functionality that I think you are after.
If setting up a CMS is not something you want to begin doing then I would also look into storing the list of servers in a text file and using something like
foreach ($server in (Get-Content C:\myservers.txt)){Write-Host $server;}
or something similar with the servers stored in a utility database somewhere instead of a text file.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
December 26, 2012 at 6:46 am
Thank you both (Gazareth & opc.three) for taking the time to reply. I will likely end up going the route of a servers.txt file, I was just trying to find a way around it and in typical fashion was probably over thinking it a bit I guess. In any case, I do appreciate the feedback.
DT
December 27, 2012 at 6:40 am
You could use the stucture available in SQLPS. Set your location to SQLSERVER:\SQLRegistration\Database Engine Server Group\<your group name> then set a variable equal to get-childitem and do a foreach loop over each server in the group.
A simple example:
Set-Location SQLSERVER:\SQLRegistration\Database Engine Server Group\<your group name>
$servers = get-childitem
foreach ($server in $server) {<do something herer>}
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
December 27, 2012 at 8:54 am
MG-148046 (12/27/2012)
You could use the stucture available in SQLPS. Set your location to SQLSERVER:\SQLRegistration\Database Engine Server Group\<your group name> then set a variable equal to get-childitem and do a foreach loop over each server in the group.A simple example:
Set-Location SQLSERVER:\SQLRegistration\Database Engine Server Group\<your group name>
$servers = get-childitem
foreach ($server in $server) {<do something herer>}
I like the text file or database table only because it's portable. Here is more info on it. It requires the installation of some add-ons to make sqlps importable into your PoSh sessions.
Programming SQLRegistration in the SQL Server PowerShell Provider
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
January 2, 2013 at 4:50 am
MG-148046 (12/27/2012)
You could use the stucture available in SQLPS. Set your location to SQLSERVER:\SQLRegistration\Database Engine Server Group\<your group name>
Nice, didn't know about that location! Certainly easier than parsing the XML file!
July 13, 2016 at 2:53 am
This also works
get-childitem 'SQLSERVER:\SQLRegistration\Central Management Server Group\
SQL DBA
Every day is a school day, and don't trust anyone who tells you any different.
http://sqlblogness.blogspot.co.uk
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply