Brad Marks
bradm at blackforestltd.com
Fri May 23 16:01:55 CDT 2014
Jim, Good question. This is a bit of a different animal. It is a very complicated report that has very complicated underlying queries. It is run as a scheduled job at night in unattended mode. Because it is being run in unattended mode, the run time is not critical. However, when the run time doubled when we tested it on a brand new, very fast machine, I became curious why this should happen. Our "on demand" reports all run in 1 - 10 seconds. They need to be fast, as users are waiting for them. Brad > On May 23, 2014, at 2:53 PM, "Jim Lawrence" <accessd at shaw.ca> wrote: > > Hi Brad: > > My only question is why did you tolerated the system taking 14 minutes to run a report...that in itself was unacceptable. > > Jim > > ----- Original Message ----- > From: "Brad Marks" <bradm at blackforestltd.com> > To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> > Sent: Friday, May 23, 2014 5:56:04 AM > Subject: Re: [AccessD] Access 2007 Runtime on Windows Server 2012 R2 - Long Running Report Jobs > > Jim and Darryl, > > Thanks for the advice to use a view or SP. I plan to look into this down the road. > > For the short term, I would really like to understand why our reports are running much slower with the new server as shown by the info below. > > > > > Old Server (about 10 years old) > Access 2007 Runtime > Report800 - 14 Minutes > > > New Server (much faster processer and a lot more RAM) > Access 2010 Runtime > Report800 - 31 Minutes > > > I believe that there is some other factor coming into the picture here that I don't understand. > > 64 Bit OS ? > Printer Assignments ? > Access 2010 ? > Sunspots? > Demonic forces? :-) > > Thanks, > Brad > > > > > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl Collins > Sent: Thursday, May 22, 2014 9:52 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Access 2007 Runtime on Windows Server 2012 R2 - Long Running Report Jobs > > Yeah. Same here. > > Run the query as a view or SP server side and pull only the results into a temp local table and then do your thang from there. Remove temp data when finished. > > Cheers > Darryl. > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence > Sent: Friday, 23 May 2014 12:43 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Access 2007 Runtime on Windows Server 2012 R2 - Long Running Report Jobs > > Historically, pass-through reporting is excruciatingly slow. > > I have always use a SP to gather the report info, downloaded the data to a local dummy table and printed locally. This process can reduce report start times from 30 minutes plus to a couple of seconds. > > Check out the ancient solution: http://www.databaseadvisors.com/newsletters/newsletter112003/0311UnboundReports.asp > > Not all of the sample is necessary just the core code of around a 50 to 60 line solution. > > HTH > Jim > > ----- Original Message ----- > From: "Brad Marks" <bradm at blackforestltd.com> > To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> > Sent: Thursday, May 22, 2014 2:24:35 PM > Subject: Re: [AccessD] Access 2007 Runtime on Windows Server 2012 R2 - Long Running Report Jobs > > All, > > Thanks to everyone who shared their ideas and insights on this topic. > > I downloaded and installed Access 2010 Runtime this morning. > > I have run a number of small tests and so far everything works nicely. > > However, all of the reports seem to run MUCH longer than before (about twice as long). > > Example - > > Old Server - Access 2007 Runtime - Report800 - 14 Minutes New Server - Access 2010 Runtime - Report800 - 31 Minutes > > I sort of remember earlier posts here on AccessD regarding excessive run times. It seems like someone suggested possible "printer issues", but I can't remember for sure. > > Any ideas on these extended run times would be most appreciated. > > Thanks, > Brad > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman > Sent: Thursday, May 22, 2014 6:04 AM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] Access 2007 Runtime on Windows Server 2012 R2 > > > Use 2010 and if you can, 2013. Although be careful with 2013. Many client > DB features were removed. A2010 is the last full featured version of > Access for client(desktop) DB's. > > There was a bug in JET/ACE in relation to multi-core processors running under 64 bit OS's. Not sure when it was fixed. Microsoft was pretty mum about it (it's never been documented to my knowledge). > > 2010 should certainly have the fix, but A2007 may not. It was discovered when Windows Server 2008 R2 was released. > > Jim. > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Brad Marks > Sent: Wednesday, May 21, 2014 10:55 PM > To: Access Developers discussion and problem solving > Subject: [AccessD] Access 2007 Runtime on Windows Server 2012 R2 > > All, > > We have a small Access 2007 "Runtime" application that runs under Windows Small Business Server 2003. This scheduled application runs every night in an unattended mode. It pulls data from a SQL Server database and generates several reports (PDF) that are automatically e-mailed to select employees. > > We are now migrating to new server hardware which will be running Windows Server 2012 R2. > > Will an Access 2007 (Runtime) application work properly under Windows Server > 2012 R2? > > Would it be better to use Access 2010 Runtime? > > 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 > > -- > 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 > > -- > 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 > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com