TMS 11 SQL Database

[Shawn Jones]

I am finalizing the paperwork (Change Management, etc.) to get my TMS server and software installed and have a question about the SQL database that TMS generates.

I am going to be managing about 40 systems, no infrastructure units as of yet (in the next few years though). What would the average size of the database be on the SQL server? I just know I am going to be asked this question by my server farm folks.

I am in the home stretch :banana: ...I had to purchase my own server, and for it to be company spec, was an HP Server, at $8k + software. TMS will be the only thing running on it, should be blazing fast.

Thanks

[Morgan81]

We're going to be managing a few more systems than that with no infrastructure yet as well and we're expecting 200mb a year growth.
We also have a standalone server for our database as well.
We also had to buy a company spec'ed server so I think we have about 25 gbs of breathing room.

[Shawn Jones]

Unfortunetly, or fortunetly, however you would like to look at it, this is the first time I have set up a server, but our IT department has been great at assisting. They are just a bit leary about introducing another app/server/SQL DB in to the production environment.

I work for Limitedbrands (you know Victoria's Secret, Vicky's Catalog, Express, Limited Stores), and have been here about 8 months as the AV Conferencing Analyst. I am hip to making the inventory run at it's peak, just not server setup and administration. Let me tell you, I am learing a bunch during this process. Trying to get approved and scheduled for the TMS Admin course as soon as possible as well.

[Morgan81]

If you are just going to be monitoring and managing your endpoints, you should be fine with the standard MSDE database. At a former company, I had approximately 200 endpoints in it and we never saw a problem. The reason you would like the dedicated server is so you can schedule with it or have many users accessing TMS at the same time. If you do not see that happening, you'll be fine with MSDE.

[Shawn Jones]

I am going to go ahead with the full SQL DB, I have the Client Solution Package included with 25 users. Might as well do it now, instead of later.

[djackson]

We use TMS 10 to manage 16 codecs, a tandberg Gateway and a Tandberg MCU for the last three years.

Since April 2005, the total database size is 67 megs - which includes SQL administrative overhead. The size for TMS database is 23 megs. In April of 2005 after we upgraded to TMS 10, we rebuilt the system because there were so many bugs left over in the database from TMS 8 & 9.

I have generally been disappointed with TMS.
1) Lot's of bugs in the past (mostly 8 & 9) and limited functionality.
2) Very slow product.
We like to monitor conferences in REAL time, and TMS has unacceptable lag. The end result is that we stopped using TMS and started managing all conferences directly through the MCU or codec interfaces.

In my opinion TMS should be able to reproduce near 100% of the information from the endpoint, gateway or MCU web pages with full functionality. TMS 10 does not do this, hopefully TMS 11 will.

There are some users of TMS10 whom I'ved talked to who love the product and see no flaws - so this is just my opinion.

[Sean Lessman]

In my opinion TMS should be able to reproduce near 100% of the information from the endpoint, gateway or MCU web pages with full functionality. TMS 10 does not do this, hopefully TMS 11 will.

Hi djackson,

TMS 11 has had significant development towards deeper control of the MCUs etc. You should take a look. As always you can download the free version, or ask a TANDBERG representative for a demo.

Sean

[Shawn Jones]

Another question on the full SQL DB, my DB admins only want to grant SA access to the server for the installation, but then set up an account for the running of TMS.

What are the parameters/permissions that TMS should be included in that user account?

Anyone had to do this?

The DB will be running on our Production cluster, so the DBA's are a bit unwilling to grant all access.

Thanks

>>The DBA's ended up setting up a user name with admin access similar to a SA, and i have been utilizing that without problem.