[AccessD] Job Duration Puzzler - Access 2007 Report

Rocky Smolin rockysmolin at bchacc.com
Mon Sep 16 14:32:50 CDT 2013


WAGS:

Other jobs running at the same time now that weren't running before taking
machine cycles?  Change in priority of your job? Can you monitor the Task
Manager for the server while your job is running to see what else might be
going on?

R
 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Brad Marks
Sent: Monday, September 16, 2013 12:25 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Job Duration Puzzler - Access 2007 Report

Rocky,

Yes, it is running entirely on the server, pulling data from a local
SQL-Server database.

Brad  

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Monday, September 16, 2013 2:21 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Job Duration Puzzler - Access 2007 Report

Is it running entirely on the server with nothing coming across the wire?

r 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Brad Marks
Sent: Monday, September 16, 2013 12:15 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] Job Duration Puzzler - Access 2007 Report

All,

We have a high level Access 2007 Report that is generated every night.
The data for this report is pulled from a number of SQL-Server database
tables. 

This report is automatically generated nightly on a server with these specs
- MS Window Server 2003 R2 Enterprise Edition SP2 2.50 Ghz
12 GB Ram

About a month ago, I noticed that the "run time" for generating this report
went from 8 minutes to 20 minutes.  Everything works fine, except that the
run time has more than doubled.

I can also run this same report on a stand-alone PC with these specs -
Windows XP SP3 2.50 Ghz
3.25 GB Ram

When the same report is generated on this PC, the job runs for about 8
minutes.

Over the weekend, when nothing else was running, I conducted a number of
tests to confirm what I was seeing.

The results were consistent.  The generation of this report takes more than
twice as long on the Server as compared to the PC.

I am very puzzled and not sure where to look.

I don't know why the run times went up dramatically on the Server.

I don't understand why the run times vary between the two boxes.

Any insights or advice would be most appreciated.

Thanks,

Brad    
   



--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
This message was scanned by ESVA and is believed to be clean.
Click here to report this message as spam. 
http://h0stname/cgi-bin/learn-msg.cgi?id=26A7228C9A.3C04B



--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list