
Laddy20 asked a question.
Used this query but the output doesn't make sense.
Select ai.Created, c.lastscandate,c1.*
From SnowInventory.inv.AssignedId ai
INNER JOIN SnowInventory.inv.AgentManifest am ON am.AssignedId = ai.AssignedId
INNER JOIN SnowInventory.inv.DataClientView2 c1 ON c1.ClientId = am.ClientId
Inner join [SnowLicenseManager].[dbo].[tblComputer] c on c1.HostName = c.hostname
where c.IsServer=1 and datediff(DAY, ai.Created, getdate())<=7
Order by Created Desc
How is it possible created date is July 6th but the last scan date shows July 3rd if this this record was created first time July 6th
With all the due respect. As the Snow databases are not officially documented and you pick some more or less random information from the database, not knowing what the real information is, this is the expected result in my humble opinion.
You check a "created" on a table "AssignedId" that links to "Agentmanifest" that obviously refers to the installed agent version.
We had this duscussion before, and if I recall this correctly, it resulted in using the "client install date" as the best reference you can get in SLM.
So either use this in an SLM computer report, or maybe use SnowInventory.inv.Clientconfiguration.created instead.
I think there is nothing that gets closer in the Snow data.
@Axel Lamparth​ , this is not entirely true ...
Eventhough the datamodel is not officially documented, the query on itself is very correct.
The created date in the database is the date when the clientid record was created, so the first time the agent was able to communicate with the server either from a heartbeat manifest or from a snow inventory package.
In the above example where there is a difference between lastscandate (July 3rd) and created (July 6th), the client was obviously not able to communicate with the snowserver before the 6th.
Just take note of the fact that timezones might play a difference as well, whereas the created timestamp is the timezone of the master inventory server and the lastscandate is the timestamp from the local machine where the agent runs ....
Normally when checking deployments, you have the following identifiers