Software Metering Questions

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hello Champions,

Greetings!!

We have SMS 2003 Sp3 with SQL Server 2005 Sp2 and around 8000 Vista client
machines in our hierarchy. Currently we are slowly moving our SMS 2.0 client
into SMS 2003 environment. Within 8 months it should touch 22000 client
counts!!

We are in a process of enabling software metering and would like to clarify
couple of queries that I have.

IMPACT:

• Can you get more information about the amount of additional SQL
database storage will be required on primary databases, as well as on the
central server? Ca you provide an impact statement of how much you think this
will be increased based on a rough idea of how many rules we will implement
• Can you investigate the average network impact per rule per client?
• Any client performance impact info? (i.e. will they know this has
been enabled)?
• Any best practice recommendations on how many rules we can create
without impacting any of the above areas

SETTING SCHEDULES:

• Are there any best practices or recommendations on setting times
and schedules other than the defaults?
For example if I have 14 rules enabled what will be the network traffic? 27
kb network traffic per client per day(As per capacity planner) is this per
rule or 14 rules? Can you confirm this? If the client is only reporting once
every 7 days (the default) – is this still true? And sorry, but is this
software inventory, metering, or both?
SQL database impact. Have you any other data on how large the database will
increase based on, say 10 rules and x number of clients?

Let’s say if I have 15 rules per client (client reporting on every 7 days)…
so as per the current client count we have, i.e. 8000, what will be the DB
growth?

Many thanks for your valuable answers 

Regards,
Jaison

.

Relevant Pages