Windows 2008 SBS 64-bit

George flowersoft at compuserve.com
Mon Oct 26 21:13:57 PDT 2009


I also have a couple of customers running filePro on Windows 2008 SBS 64-bit
servers with no speed issues at all.  If anything, they seem to run quite a
bit faster than the Windows 2003 SBS 32-bit servers.  Some programs that I
use with filePro, such as Norton's old ask.exe program, do not work from
computers running a 64-bit version of Windows but run from a computer
running a 32-bit version that is connected to a 64-bit server.

-----Original Message-----
From: filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.com
[mailto:filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.com]
On Behalf Of Richard Kreiss
Sent: Monday, October 26, 2009 4:06 PM
To: john at valar.com; ryanx at indy.rr.com; filepro-list at lists.celestial.com
Subject: RE: Windows 2008 SBS 64-bit



> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
[mailto:filepro-
> list-bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of John
Esak
> Sent: Monday, October 26, 2009 3:39 PM
> To: ryanx at indy.rr.com; filepro-list at lists.celestial.com
> Subject: RE: Windows 2008 SBS 64-bit
> 
> Ryan,
> Tim has proven a strange thing to jme over and over. I wouldn't have
> believed it if I didn't see it myself.  I'm not sure if this is your
issue,
> but you might as well be cognizant of it anyway.  Apparently, there is
some
> different methodology to writing files and their sizes and etc., etc. on
the
> Windows file systems and O/S's. If you allow a file to grow record by
record
> and there are lots of olks adding new records to the end of the file
> regularly, the slowdown is actually VERY noticeable.  So, Tim's workaround
> (and indeed filePro's old workaround from the days when this was
ubiquitous
> behavior) is to pre-expand the file by a hundred thousand records or
> whatever value won't be reached quickly.  Then it's not a matter of
actually
> growing the file with each new record addition as you know. It's just
> indexing out to the record and filling in space that's already there.
> 
> Now, on Unix, and Linux this simply is NOT an issue at all.  Could it be
> what it hassling you though?
> 
> Nancy, has lots of experieince with Windows... So does Richard Kreiss.
> 
> 
> John
> 
> 
> > -----Original Message-----
> > From: filepro-list-bounces+john=valar.com at lists.celestial.com
> > [mailto:filepro-list-bounces+john=valar.com at lists.celestial.co
> m] On Behalf Of Ryan Powers
> > Sent: Monday, October 26, 2009 3:18 PM
> > To: filepro-list at lists.celestial.com
> > Subject: Windows 2008 SBS 64-bit
> >
> > I have a question from someone regarding the platform stated
> > in the subject
> > line.
> >
> > A filePro user "upgraded" to this system and the performance dropped
> > dramatically.
> > Does anyone have any experience with this platform or the
> > issue? Is there a
> > solution?
> >
> > Thanks.
> >
> >
> > _______________________________________________
> > Filepro-list mailing list
> > Filepro-list at lists.celestial.com
> > http://mailman.celestial.com/mailman/listinfo/filepro-list

Have a Client running Win 2008 on 2 new servers both Quad Core.

One is strictly running terminal server and the other is the database
server.   They have both internal and external people accessing the system.

In addition to this, both their  servers is being mirrored, real-time, over
the internet, to an outside location to their old equipment running Server
2003.

They have not had any performance problems.

My questions:
	1. What Version of Server 2008 was installed
	2. Was this a clean install or upgrade
	3. How much Memory on the server
	4. What processor on the server
	5. As previously asked, is there anti-virus software running on the
workstations?
	6. Is Vista running on any of the workstations
	7. Have they encrypted a drive, folder or file using Bit_locker?

If there is Anti_virus software running, make sure it either excludes
filePro executables from checking or is manually informed to always let the
fp executables run without checking.

This can be a major pain if there are a lot of workstations to configure.


Richard Kreiss
GCC Consulting
rkreiss at gccconsulting.net
  




_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
http://mailman.celestial.com/mailman/listinfo/filepro-list



More information about the Filepro-list mailing list