I'd have to sit down with the logic - but you could create a class, and have the discovery some kind of expression where "Windows Computer host contains SQL database where databasename = foo"
From: [email protected] [mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey Sent: Wednesday, May 13, 2015 5:30 PM To: [email protected] Subject: [msmom] Discovery w/ VSAE Authoring I'm currently using VSAE for MP Authoring and I've been following Brian Wren's MP Authoring workshop. I'm going through discoveries and views for an internal application. The application resides on two servers-an application server and the backend SQL server. The application server I am able to discover via registry. The database server running SQL does not have other unique properties within the registry to target. I'm not sure how to proceed with discovering the SQL database for my "Internal Application Database" class. I know the SQL database is (for example) called "Internal_App_DB". Because "Internal_App_DB" is already discovered via the SQL MP, is there a way to take "Internal_App_DB" and include it in my "Internal Application Database" class? I want to create a "Database" state view folder. The folder should only contain the "Internal_App_DB" database. I am not sure how best to go about this task and my online searching has not yielded any results. I cannot find if WMI exposes the database names in some way. I do know the registry does not contain any unique information related to the database. This can probably be accomplished with a script discovery, but before going down the path with the most processing overhead, I was curious if I could piggyback off the SQL MP discovery to include the "Internal_App_DB" database in my state view? If that's not clear, I'm happy to provide additional detail. I'm not asking for the MP to be written for me, I'm happy to do additional reading if anyone can provide helpful materials. I've just come up against a wall and looking for a boost. Thank you. -Geoff Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you.
