Assessing needs to install one more SQL server for MOM

I am trying to avoid installing more SQL servers than what I need. This is
the scenario, please let me know if I have justification to buy a SQL server
license to install MOM on local computer or I can use this on my MainSQL
server instead:
a) I need to configure such SQL server for MOM and MOM best practices
require to allow only "Windows authentication". I have virtually dozens of
third-party applications that rely on that SQL server and I do not know if
by changing configuration to "Windows authentication only" to satisfy MOM
setup that could eventually break something down the road.
b) I have to enable IIS on such SQL server box. CUrrently MainSQL server has
no IIS enabled. That would be just a security issue, but I guess so many
applications require to have IIS installed these days...
Do you think the above is enough to make me buy a SQL server license
dedicated for MOM ?
And a poster kindly reminded that instances would do work here and allow me
to configure the "Windows authentication only". From reading the SQL help
files, I see that instances are generally not recommended for SQL-production
environment (this is my case here, I will be using MOM in production
environment).
If you have any input on how SQL instances are doing in real world, please
let me know.
"Marlon Brown" <marlon_brown@.hotmail.com> wrote in message
news:eBkAAqU4EHA.708@.TK2MSFTNGP11.phx.gbl...
>I am trying to avoid installing more SQL servers than what I need. This is
> the scenario, please let me know if I have justification to buy a SQL
> server
> license to install MOM on local computer or I can use this on my MainSQL
> server instead:
> a) I need to configure such SQL server for MOM and MOM best practices
> require to allow only "Windows authentication". I have virtually dozens of
> third-party applications that rely on that SQL server and I do not know if
> by changing configuration to "Windows authentication only" to satisfy MOM
> setup that could eventually break something down the road.
> b) I have to enable IIS on such SQL server box. CUrrently MainSQL server
> has
> no IIS enabled. That would be just a security issue, but I guess so many
> applications require to have IIS installed these days...
> Do you think the above is enough to make me buy a SQL server license
> dedicated for MOM ?
>
|||They are harder to manage because now you have two sets of executibles that
must be serviced and could be corrupted by OS fixes including two sets of
perf counters, etc., etc., etc.
I'd consider running MOM on another server that's less used. You should
never run the monitoring process on the item that you are monitoring. You
will affect the outcomes of those observations. Your management pieces
should always be on another host and do their monitoring remotely.
Sincerely,
Anthony Thomas

"Marlon Brown" <marlon_brownj@.hotmail.com> wrote in message
news:%230%23r8eY4EHA.2196@.TK2MSFTNGP14.phx.gbl...
And a poster kindly reminded that instances would do work here and allow me
to configure the "Windows authentication only". From reading the SQL help
files, I see that instances are generally not recommended for SQL-production
environment (this is my case here, I will be using MOM in production
environment).
If you have any input on how SQL instances are doing in real world, please
let me know.
"Marlon Brown" <marlon_brown@.hotmail.com> wrote in message
news:eBkAAqU4EHA.708@.TK2MSFTNGP11.phx.gbl...
>I am trying to avoid installing more SQL servers than what I need. This is
> the scenario, please let me know if I have justification to buy a SQL
> server
> license to install MOM on local computer or I can use this on my MainSQL
> server instead:
> a) I need to configure such SQL server for MOM and MOM best practices
> require to allow only "Windows authentication". I have virtually dozens of
> third-party applications that rely on that SQL server and I do not know if
> by changing configuration to "Windows authentication only" to satisfy MOM
> setup that could eventually break something down the road.
> b) I have to enable IIS on such SQL server box. CUrrently MainSQL server
> has
> no IIS enabled. That would be just a security issue, but I guess so many
> applications require to have IIS installed these days...
> Do you think the above is enough to make me buy a SQL server license
> dedicated for MOM ?
>
|||I agree. I will buy a SQL server license now !!!.
"AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> wrote in message
news:%23frmjIe4EHA.3864@.TK2MSFTNGP15.phx.gbl...
> They are harder to manage because now you have two sets of executibles
> that
> must be serviced and could be corrupted by OS fixes including two sets of
> perf counters, etc., etc., etc.
> I'd consider running MOM on another server that's less used. You should
> never run the monitoring process on the item that you are monitoring. You
> will affect the outcomes of those observations. Your management pieces
> should always be on another host and do their monitoring remotely.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Marlon Brown" <marlon_brownj@.hotmail.com> wrote in message
> news:%230%23r8eY4EHA.2196@.TK2MSFTNGP14.phx.gbl...
> And a poster kindly reminded that instances would do work here and allow
> me
> to configure the "Windows authentication only". From reading the SQL help
> files, I see that instances are generally not recommended for
> SQL-production
> environment (this is my case here, I will be using MOM in production
> environment).
> If you have any input on how SQL instances are doing in real world, please
> let me know.
>
> "Marlon Brown" <marlon_brown@.hotmail.com> wrote in message
> news:eBkAAqU4EHA.708@.TK2MSFTNGP11.phx.gbl...
>