Remote Database Install Question

Usage and Config Platform
1

(imported topic written by SystemAdmin)

I’m setting up a new TEM 8.2 environment on Windows 2008 R2. We ran a small 30 day demo on older hardware and now we are installing on new hardware with our production license.

In the demo, we ran everything on the c: drive and used the default SQL Express database. Easy.

I already have a production SQL server with only the default instance and only a few databases on it. However, we’re contemplating buying another copy of SQL 2008 R2 standard because of this document that was given to us by a consultant:

https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Endpoint%20Manager/page/Remote%20Database%20Guide

It seems a rather painful process. Is it really that bad? Can’t I just create a sql user with sa rights on the remote sql server and use that info when creating the database in the TEM install (selecting “remote database” and choosing the default instance running on the server)?

Finally, is there any big advantage in going local versus remote? I have it running local at the moment, but having gone through the install today, I’m not happy with everything and may just start from scratch (I’m assuming that’s not a big deal as long as I have my masthead, license and keys available).

Thanks,

TMR

2

(imported comment written by SystemAdmin)

Unless you “need” the database to be remote, I’d recommend leaving it local on the TEM server with the default configuration.

A local database means simpler upgrades later, and you should get better performance out of it depending on the size of your install.