Sue_H (9/13/2016)
I don't know if it's deliberate or not but typically for your own management type of application they encourage the use of SMO since that's what it was designed for. You may want to look at utilizing that instead of shelling out to SSMS...which as you found likely doesn't work anyway.Sue
Sue, thanks for your reply.
I already use SMO inside our application, it's technology is irrelevant for what we need, the purpose of the tool is not to replace SSMS.
The application is a global monitoring app, which helps us to globally check things like disk space etc.. As this information is not available from within SQL Server (we use mounted disks which are not readilly available to the OS) we need to work outside the box using tools such as this.
A datagridview is filled with SQL servers that have 'one problem or another'. So it's only a KPI program (read: monitoring tool). From there we administer our SQL servers as one always would, using SSMS. It was never the purpose of this app to replace functionality within SSMS.
Right now we need to manually start SSMS, or manually connect to servers that have an issue. It would be handy to be able to double click an entry, so that SSMS automatically connects to that server, such basic commandline functionality is very standard in most other maintenance tools and applications.
Compare it to doubleclicking a JPG file and not have Adobe Photoshop create a completely new instance of itself, but reuse the existing running executable, merely opening it in a new window.