Accounts not being found in SQL SE (sometimes

Hi bit of a strange one that I said Id log on here, to see if any other partners have experienced this

Migrated a VFP site to SQL SE

USers search for a sales or purchase account using the ACCOUNT number (as they know them all)

"Now & then" it cant find it. they try it again....still cant....they try again & it finds it!

I cant think of what we can do, as theres no UDS in SQL SE & as its intermittent, we cant recreate it - just wondered if anyone else has this "out there?"

thanks

Find more posts tagged with

Pegasus - Partner General Discussions

Accepted answers

All comments

tcyprys

Not really had anything like that - we do have a large site that processes huge PL and SL and that hasn't ever been reported.

The only thing initially they were getting was a Switch to/retry message - I wonder if this is similar without the message popping up? That was turned out to server setup and delays in processing from the server... but if they are generally happy with performance, it is not likely to be that...

The only other thing that sprung to mind was the old 'Windows 10 1803' update type problem... that had delays on the client ...but that is a long shot!

Tony

unknown

cheers Tony - yeah its a strange one!!! But thanks for your input

unknown

Hi tony, clients are also getting the switch to message - theyre keen to know what was changed on the server - as it could help them, would you be able to confirm pls. Appreciate this

tcyprys

Hi James,

It was their IT that sorted the issue - we narrowed it down by proving it must be the live server by setting up a test system on their network where no-one got the issue (it was a long arduous process!).

They stated it was 'disc access' on the server that was slowing the process down i.e. they reckoned that because we still use VFP with the product, and the fact there were 7 or 8 other SQL instances/applications using the same server, this caused resource issues for 'disc access' - the eventual solution was to install Opera SQL on a separate SQL Server.

This has so far been working fine for them for the past 6-10 months...

The only thing is, their IT may have been saying this to cover themselves but in farness, it did appear like a resource issue.

Unfortunately, I don't have any further detail regarding that as the DB admin who oversaw that investigation is no longer with them. So it depends if you have the option to setup a test server on their network and test it to kind of prove it is environment. (Pegasus did dial in at one stage to assess the original SQL setup and did agree that all, from a SQL point of view, was fine).

Hope that might help in some way

Tony

Copyright © 2025 Infor. All rights reserved.