1. PDQ Deploy & Inventory Help Center
  2. Community
  3. PDQ Inventory
 

Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

best practices for installation of PDQ Inventory between 2 person IT shop

Avatar
Shawn Done

Hello,

We have a 2 person IT shop and I have been curious of the best way to install PDQ Inventory and PDQ Deploy for that matter so that we can both utilize the same database.  We have one license of each right now but with 2 people accessing the databases of both products I will probably need to purchase another of each correct?

Do we then each install the application on our workstations and can we locate the.db files to a shared folder that both workstations can access?  Can the .db location be changed?  
OR do we need to install both apps on a server where the .db file would be located on the server's programdata folder.  We would then each need to remote into the server to access the PDQ applications?  Found running the apps on the server is quite a bit slower and frustrating. Would like to do the local install and share database method if we could.

What are others doing or what is the best practice?  I know when running it on my workstation before tying it on the server, it was much faster locally.

Thanks.

Shawn

0

Comments

5 comments
Date Votes
  • Avatar
    Shane Corellian

    Hi Shawn,

    Yes, the licenses are per user so two users would require two licenses.

    Both PDQ products were designed to be used by one user per database. At this time there isn't a way to share multiple databases. You'd still need to have each user use the same DB on a server to accomplish this.

    0
  • Avatar
    Shawn Done

    Thanks Shane.  Do you ever see a desktop install for both parties possible with sharing a single database on a server location?

    0
  • Avatar
    Shane Corellian

    Hi Shawn,

    Yes, we do have plans to accommodate shared DB functionality... we don't have an estimate yet.

    0
  • Avatar
    Shawn Done

    THanks again.

    0
  • Avatar
    Shane Corellian
    **Update** - We recommend utilizing the Shared Databases and Scan Caching feature introduced in 3.1. While this is still not a true single DB solution it resolves most of the issues that arise with multiple databases such as duplication of scans and Collections. Let us know if you'd like us to elaborate on these features.
    0