Not really sure where to post this.  Relates to SQL Server, ODBC/FMSQL and FM Server.

 

I have installed the FM ODBC Drivers on our SQL Server (2005) Machine.  I created Linked Servers to multiple FM 12 Databases, on FM Server.  I am creating a central SQL Server Table, for some Marketing Data.  Same thing as the last post.  Just a different approach.

 

Works okay, for the most part.  I issued a couple SQL Statements, which overloaded FM Server.  Won't do that again but not uncommon in Database World.  FM Server is certainly limited on this end though.  I have simplified my SQL work to pulling individual tables from FM Server & doing the dirty work in T-SQL.  Again, not uncommon in Database World.

 

I have watched FM Server as this progressed though.  FM Server Cache rarely, if ever gets hit.  The data is there.  The fmxdbc_listener Service certainly gets busy but does not overload the machine.

 

The data transfers in chunks.  I get a few hundred records, then I wait for 5-20 seconds.  Wicked delay.  Not horrible but should run a lot faster.

 

What stands out on FM Server is that the Disk Writes just soar.  Very little Disk Reads, 15-20 KB bytes per second, at most.

 

The Disk Writes jump to 500 KB/Second.  I am just doing Selects, Read Only.  Not updating anything.

 

FM Server is probably building the entire return data set & having to store it on disk.  Thrashing.

 

I doubt that we can do anything about it, with limited server settings.  Mostly informational, for anybody who is trying to extract data from FM.

 

Overall, I am happy with it.  Pulling data only from the Server though, it should be a lot faster.

We added 2 Gig of RAM to our FM Server over the weekend.  All speed issues, both SQL & FileMaker, cleared up.  That gives us 3 Gig for FM Server Cache, on 5.8 Gig of files.

 

Whatever works.