Installing Oracle OEM Grid Control is not rocket science but certainly is not an intuitive point-and-click windows-alike any-day task.

I would strongly suggest to get your Oracle DBA working on OEM Grid Control installation and setup then, there is a "System Monitoring Plug-in for Microsoft SQL Server" which will do for SQL Server targets what "OEM Agent" does for Oracle targets.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

The metrics are defined in Metadata files and cannot be modified/customized.Any change to a metadata file not provided by Oracle through a patch or a patchset or a new plug-in release is not supported.

You can log an Enhancement Request for the plug-in Microsoft SQL Server to request changes to the current metric

Sorry not to hack this thread but , I am currently working on monitoring SQL using OEM 12c. I have seen an article which tells me that its a best practice to install OEM on windows rather than on Unix and then install SQLPlugin to monitor SQL Server?

Is it so? Or is it ok to go with Unix? Could you please throw some light on Adv and DisAdv on using Windows to install OEM.