2 Replies Latest reply on Feb 15, 2017 11:37 AM by phoffmann

    Number of PCs mismatch between Report and SQL Studio

    Asraf Radzi Apprentice

      Hi,

       

      I'm doing checking on the Reports result/output using SQL Studio and found out that the numbers of PC in the Reports is mismatch to numbers of PC in SQL Studio. The database is in Rollup Core.

      The SQL query statement that I used at SQL Studio is based on Query that I created (Queries > Right click created query > Inspect > Generated SQL)

       

      What are the possibilities that the numbers of PC is mismatch between Reports and SQL Studio both is generated from the same database (and same SQL statement)?

      sql_query.png

        • 1. Re: Number of PCs mismatch between Report and SQL Studio
          masterpetz ITSMMVPGroup

          Hi,

           

          the job of a rollup core is to consolidate multiple core databases into one database. When you create a query on core A, the result will be different if you do the same query on the rollup core’s database because it holds the information from all connected cores. Are  you sure that you were connected to the rollup core with your LDMS console, when you execute your query? If so, the results should be the same…

           

          Regards

          Christian

          • 2. Re: Number of PCs mismatch between Report and SQL Studio
            phoffmann SupportEmployee

            ... also, in addition to Christian's explanation (great job!) there's one additional thing to remember.

             

            Scopes!

             

            SQL Studio will run in a "all devices" scope, since it doesn't know about them and just reports on the data. Where as a REPORT will (always) respect scopes, because LANDesk will make sure that those apply (and people can't access / do stuff to devices that they shouldn't be able to see).

             

            That one tends to trip some folks up some times (i.e. - situations where people SHOULD have "all devices" but don't for some reason).

             

            That's usually the 2 possibilities in this sort of situation.

             

            You can always try to find a device that's listed in your SQL report & not your "proper report" (or LD query) and work out from there in a reverse-engineering kinda way why you might not be seeing it (tends to reveal some "duh - didn't think of THAT" type thing usually).

             

            Hope that helps .