PI and SQL Server

Started by Gareth Watkinson

Gareth Watkinson

PI and SQL Server   25 April 2006, 17:00

Hi,

I've got PI installed on 2 print servers and have configured it to write into a single SQL database. However i find whenever i add printers it deletes all existing printers in the printers table in SQL (i.e. only the last set of printers i add are listed).

Is this by design? Should i create a new database for each print server?

Thanks,
Gareth
SoftPerfect Support forum - Andrew avatar image

Re: PI and SQL Server   25 April 2006, 19:34

Ah, this is a bug. The problem comes from the design when Print Inspector supported just a single local database. Currently, I would recommend to use different databases for two Print Inspector instances. I hope we'll fix it shortly.
Gareth Watkinson

Re: PI and SQL Server   25 April 2006, 21:23

OK Thanks.
Scott

Re: PI and SQL Server   24 May 2006, 01:00

When will the fix be available as I have 20-30 print servers which i'd need to install this on and do not want 20-30 databases.
SoftPerfect Support forum - Andrew avatar image

Re: PI and SQL Server   24 May 2006, 01:44

Yes, this issue has been fixed in a build of the 15th of May. Simply download the current installation package and install it over the previous release.
Salvador Diosdado

PI and SQL Server   25 October 2009, 15:09

Well, I'm a beginner trying to use PI to generate reports from data base in SQL, can you suggest the best and quickest way to learn?..where can I find examples?. any suggestion would be appreciated.
SoftPerfect Support forum - Andrew avatar image

PI and SQL Server   25 October 2009, 15:48

Sometimes you can get the answer faster if you try the forum search and/or have a look at the software user manual to see if your question has already been answered.

Our forum rules are simple:

  • Be polite.
  • Do not spam.
  • If possible, check your spelling and grammar.

Author:

Subject

A brief and informative title for your message, approximately 4–8 words:

     

Spam prevention: please enter the following code in the input field below.

 ********  **     **  **          ******   ******** 
    **     **     **  **    **   **    **  **    ** 
    **     **     **  **    **   **            **   
    **     **     **  **    **   **           **    
    **     **     **  *********  **          **     
    **     **     **        **   **    **    **     
    **      *******         **    ******     **     

Message: