Client Management Suite

 View Only
  • 1.  Exporting data then back end sql delete in sql table

    Posted Apr 14, 2016 08:16 AM

    So I started at a company 5 years ago. They were on Altiris CMS 6.0 and had a process which allowed them to have a sql dba export records into an archive table. Then go in and run same query but with a delete to remove these records.

    This was done for a few reasons.

    1. Patch management did not release license when machines were retired so when you delete they would retire.
    2. Keep a smaller DB size for performance

    Now I understand item 1. but I do question 2. I feel that doing a backend sql delete could create orphaned items and actually create more errors in the logs and also performance issues.

     

    so Altiris still functioned and we went to a new server for CMS 7.1 SP1 but kept the same DB. Then went to CMS 7.5 Sp1 HF5 which changed the db schema and now we are on 7.6 HF7.

     

    So I am curious as it is time to do another archive on other peoples thoughts or if they do archives how.

    So few questions:

    1. How big of a CMS DB will cause performance issues? 
    2. Could this create orphaned items as I am thinking?
    3. Could this cause actual performance issues?
    4. Do you archive and how?

     

    so our archived data is SWD records older than 210 days. We also archive computers that are retired older than 210 days. SWD records are deleted via SQL back end but the retired computers are deleted from the actual console. I think deleting from the console is the best approach as it will delete all records for that machine throughout and not create orphaned items.

     

    Thoughts?

    Thanks

     



  • 2.  RE: Exporting data then back end sql delete in sql table

    Posted Apr 21, 2016 09:48 AM

    To start with I can recommend you two tools available to download:

    SMPDiag (TECH202997)

    SSETools (INFO2568)

    With both tools you can run checks on your SMP and CMS DB. SMPDiag especially gives you directly links to possible solution if a certain problem / known issue is found on the server.

    In the SSETools you have a part under "Database Health" check there you can for example the table sizes of your CMS DB. The size does not directly means that it could be a performance problem however you might just run a search on the symantec support side if you find a table which is very large. Large tables can sometimes point to the fact that "clean-up" jobs are not running. Sometimes this clean-up can than be start manually or you need to get help from Symantec support.

    Here just an example "KNOWN ISSUE: ItemVersionData table is growing very large very quickly. - TECH46681"

    Regarding to the process of deleting. I would also suggest you do it from the console or alternative you could use ASDK. You are right this is safer as deleting directly from the database as it makes sure it removes all associations. There are also some articles out there on connect regarding the deletion of computers.

    Regarding the issue with the licenses with retired computers. If that is still the case this is definately also a case for Symantec support to fix.

    Hope this helps.

    Stefan



  • 3.  RE: Exporting data then back end sql delete in sql table

    Posted Apr 21, 2016 10:09 AM

    This might be of use too:

    Maintenance of your CMDB - analyzing the defragmentation level of CMDB and performing the defragmentation
    https://support.symantec.com/en_US/article.DOC9186.html