Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 931
  • Last Modified:

Replace command slowness - VFP in Server 2008

My company has an extensive, mission critical VFP 9 application in use in numerous sites.  One client has recently upgraded to Server 2008 R2, and running it numerous VM's (were running XP, now running Server 2008) and numerous TS sessions.  We are not explicitly limiting RAM usage (Sys(3050)) yet, but think the VMs may have a limit.  We use a standard VFP database, with extensive use of BEGIN and END transactions for data changes, no buffering.  
There appears dramatic slowing of the application at random locations, typically around record replaces.  ContrAcct had the same question a while back but a non-specific solution was forced.  We use minmal specific record locking but acknowledge this may be a factor in this environment.  
Virus control is turned off, machines are all local at the site.
Has anyone had real problems around this and identified real specific solutions?
Thanks
0
kiwivfp
Asked:
kiwivfp
  • 4
  • 3
4 Solutions
 
pcelbaCommented:
You should also turn off SMB2 and oplocks. Both on server and client side. Administrators should know how to do it.
0
 
kiwivfpAuthor Commented:
Thanks pcelba.
SMB / SMB2 was discussed this am - expect to do this today.

Oplocks was turned off from the TS client side - need to check data server and the newly created S2008 VM clients.  I think there may be issues (other external services etc) that need it on - may need to move the data to another server.

Have you actually seen this explicitly fix situations in the past?

Will let you know how we got on today

Regards
0
 
pcelbaCommented:
Yes, turning oplocks and SMB2 off was always helpful for shared file access like FoxPro or Access.
0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
kiwivfpAuthor Commented:
So we tried all these things and still had issues.  Finally got the clilent to move the data to a new Virtual 2003 dedicated server, and all seems OK.  Can't help thinking the 64 bit / Server 2008 issue may end up being a sideline and that there was an underlying issue with the original 2008 server, perhaps with a few network issues thrown in for good measure.  I will update in a few days.
Thanks all for input so far.
0
 
yoshuaCommented:
take a look at the "tcp chimney offload". Disabling this "feature" sometimes help.
0
 
kiwivfpAuthor Commented:
Thanks pcelba and yoshua for the tips.  We were still getting sundry errors in the system from Server 2003, but different - "Unable to read file ..." indicated network drop offs.  Got soem repatching of the switch and this seems to be better - almost error free after 24 hrs.  As above, can't help thinking it may have been much the same issues but handled differently by Server 2008 and reported differently by VFP.  We also found another switch for a Term Serv registry re using the same directory structure.  
There are some other sites with similar issues but again, may be new hardware and network rather than just Server 2008.
I think we'll box on with these tips - thanks
 
0
 
pcelbaCommented:
It is good to read you are getting stable environment.
0
 
kiwivfpAuthor Commented:
I think the symptoms were clouded by network issues but all tips very helpful with server 2008.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now