Up to Discussions in Asset Lifecycle Manager

This Question is Answered

1 "correct" answer available (20 pts)
2 Replies Last post: Dec 9, 2008 1:11 PM by dferrett  
dferrett Rookie
dferrett
25 posts since
Aug 10, 2008
Currently Being Moderated

Dec 8, 2008 9:20 PM

Reporting on Synchronisation Pendings

Hi,

 

I am performing a numvber of syncronisations from LDMS, and a number of spreadsheets. I need to create\export the information when I get "Pending Updates" and "Pending Inserts".

 

Does anyone know:

 

a. where in the DB this info is stored so I can generate reports on it

b. any other hints\tips on reporting or exporting this information

 

This data needs to be verified by a couple of different internal sources, before a decision can made to either 'ignore' it or 'insert' it.

 

Thanks

Dave

 

P.S. Another thing I have found is that the use if Divisions does not appear to work (ie. report all assets in Division = abc), unless the Department and\or Cost Center details are populated, and the appropriate links between these done. Anyone else seen this?

 

Thanks

Dave

IronMike Specialist
IronMike
147 posts since
Nov 28, 2007
Currently Being Moderated
1. Dec 9, 2008 11:43 AM in response to: dferrett
Re: Reporting on Synchronisation Pendings

Dave,

 

The pending inserts and updates are in the SyncException table in the ldservice database.

 

I think I know what you are referring to with the divisions. There are many tables in ALM that have foreign key relationships. You have to insert data into the database in the correct order.

 

It's the same in any database. For example, in LDMS, you can't just insert NIC, hard drive, and software information if there is nothing in the computer table, because the computer_idn is a foreign key and a required field in those tables. And you can't populate the computer_idn in the other tables if the value doesn't already exist in the computer table.

 

So you will have to insert data in the correct order. If you have any questions about a particular problem, post more detail and I'll see if I can help.

Report Abuse
dferrett Rookie
dferrett
25 posts since
Aug 10, 2008
Currently Being Moderated
2. Dec 9, 2008 1:11 PM in response to: IronMike
Re: Reporting on Synchronisation Pendings

 

Thanks Mike,

 


I understand about the relationships in the database, so I guess my gripe is (and still is), the fact the ALM documentation leaves a lot to be desired. It is detailed in some sections, but leaves out things like....to do this, click this....but does not tell you where to go in the console (or which console) to do this or that.

What it needs is a quick-start guide, or walk through in creating an asset management system. I consulted on Altiris management products for 3 years, and they had a very good Asset Quick Start guide that went through the process of setting up a simple asset management system with the product.

ALM is a far more comprehensive product, and therefore needs more time to understand the concepts, processes, etc, and this in turn requires better documentation than is currently available.

In a nutshell, I think the doco is written by someone who knows the system quite well already and assumes that the reader does also.

I have had to create a number of cases to support, to overcome what could really have been explained in the doco.


Thanks
Dave





Report Abuse

More Like This

  • Retrieving data ...
LANDesk Community powered by Jive Software's Clearspace ® Subscribe| Legal Notices| Investor Relations| Avocent| Privacy Policy © 2009 LANDesk Software