Should I put my VCenter Database on a server with other enterprise databases

[swasheck]

My sysadmin is reinstalling VCenter and would like to put the VCenter database on the db server that has all of the other enterprise databases (ERP, advancement, etc.). I'm not convinced that this is a good idea and was wondering if there would be a significant performance hit brought about by this addition.

[Troy_Clavell]

on the contrary, the VCDB, in my opinion, should be on a remote Enterprise SQL Server. Having a remote DB instance is the preferred method.

[swasheck]

So by remote are you saying that the DB server should be specifically dedicated to the vCenter database?

[Troy_Clavell · Accepted solution]

So by remote are you saying that the DB server should be specifically dedicated to the vCenter database?

no, you are just adding another DB instance to your SQL Server. Why would the VCDB be treated any differently. There is no need to build out an entire SQL Server for one DB instance, especially if you already have an existing DB Server.

[swasheck]

Ok, thanks. I just want to make sure that the users of the other applications that use the DB server won't be affected.

[Troy_Clavell]

Ok, thanks. I just want to make sure that the users of the other applications that use the DB server won't be affected.

not at all, completely isolated. That's part of the beauty of SQL 2005 and above. What happens to one DB instance would have no impact on any other instance on the DB Server.

[swasheck]

Cool. So you'd advocate separate Sql instance on the same server.

Thanks again.

[Troy_Clavell]

yes