General OPera 3 SQL SE queries

unknown

hi apologies if this sounds a basic couple of questions, but weve held back from converting existing Opera 3 VFP clients to SQL SE for a while & only starting to get into it.

Ive a couple of questions if you dont mind me asking, that arent really "support" & wondered if anyone has any suggestions.....

The Opera 3 guide advises you to leave the "common" folder where it is, on the C drive of the server, along with all the other folders in particular "backup".

Our servers usually have a C drive thats say 100GB & an E drive thats say 500GB. We normally install Opera on the larger E drive as theres more space.

Question - do partners usually move the C drive install to E:? I can see that the C drive could get full & ultimately crash the server if backups get stored in here.

Question 2 - Where does it store the PDF files?

Question 3 - Opera 3 VFP is straight forward to upgrade, you upgrade the server, then ask the users to try & log in & then they can upgrade their client (if they're a local admin) - reading the notes, it looks like youve to go round each client & run the setup.exe manually from the CD - is this right?

Question 4 - We would normally run a UDS here & there for data checking. Im aware there isnt one for SQL, but do other partners run something else in SQL?

Many thanks & appreciate any responses!!

Regards

 

James

Steve Loader

Hi James,

In answer to your questions:

Question - do partners usually move the C drive install to E:? I can see that the C drive could get full & ultimately crash the server if backups get stored in here.

I see no reason why you shouldn't create your Common folder on the E; drive, provided that you create the required share against it, as Opera SE uses th share, and not the literal path.

Question 2 - Where does it store the PDF files?

The PDF files are stored in C:ProgramDataPegasusO3 Server SERepositorySys_0Co_ZPDF - where "Sys_0" is the Opera system number, and "Co_Z" is the Opera company ID.

Question 3 - Opera 3 VFP is straight forward to upgrade, you upgrade the server, then ask the users to try & log in & then they can upgrade their client (if they're a local admin) - reading the notes, it looks like youve to go round each client & run the setup.exe manually from the CD - is this right?

Yes, I believe that you do have to upgarde each client indvidually. I don't recall Pegasus implementing the automatic client upgrade.

Question 4 - We would normally run a UDS here & there for data checking. Im aware there isnt one for SQL, but do other partners run something else in SQL?

The "UDS" of each company is run automatically when the Pegasus Opera Service starts. To check a company's data, you need to run the SAM Health Checker. You must do this to determine whether the Opera 3 VFP/SQL data contains any critical errors that would prevent the migration to Opera SE, and which need to be resolved.

Be prepared for the Healh Checker to generate thousands, if not hundreds of thousands, of errors, mainly referential integrity errors. It's normally possible to write a few VFP/SQL scripts to rectify these, so it's not quite as bad as at first sight.

We haven't yet performed a live migration to Opera SE, but I performed a number of migrations whilst at Pegasus, and have performed a number, here at Minster, on customer data, in preparation for eventual live migrations. So, on that basis, if you have any further questions then please feel free to ask.

I hope that helps

Steve