jwcolby
jwcolby at colbyconsulting.com
Fri May 7 14:55:28 CDT 2010
Yes, but it is EVERY USER. Not just the FIRST user. They load the application. The workstations themselves are awake. Now EACH USER tries to hit the SQL Server and EACH USER gets an initial delay. After that EACH user has no delay, until the next day. That does not sound like the SQL Server (or its disks) going to sleep. John W. Colby www.ColbyConsulting.com Gary Kjos wrote: > If the hard drives are set to spin down after say 2 hours of > inactivity, maybe that only happens overnight? Then the first time > someone goes after it in the morning they spin up. Perhaps someone > changed the settings on the system to save power or some process that > used to run earlier got moved earlier or later or done away with.... > Just guesses. > > GK > > On Fri, May 7, 2010 at 1:42 PM, jwcolby <jwcolby at colbyconsulting.com> wrote: >> Gary, >> >> yes, but it happens once per day on each machine. if "sleep mode" were the cause it would happen >> once per day, or intermittently throughout the day, but each machine would see it multiple times. >> This is a "one time per day per machine" kind of thing. >> >> John W. Colby >> www.ColbyConsulting.com >> >> >> Gary Kjos wrote: >>> Are the drives going into power down mode or something that would then >>> cause the lookup to not complete in teh timeout period? Check power >>> saving parameters maybe? Does it happen if someone were to do a disk >>> access like a folder list or something before the query that fails? >>> >>> GK >>> >>> On Fri, May 7, 2010 at 10:01 AM, jwcolby <jwcolby at colbyconsulting.com> wrote: >>>> Guys, >>>> >>>> I got the following in an email from a customer. Does anyone have any ideas? >>>> >>>> >John - For the past 3 months (or so) there seems to be a problem regarding the access to the check >>>> info that resides on the SQLSERVER on PSSERVER. >>>> >>>> >The pattern we seem to be seeing is that the first time someone tries to access the check info in >>>> DISCO the check screen fields display "?????" . When They get out and go back into it again the >>>> check info is present. Then for the balance of the day all is fine. >>>> >>>> >John says he has a similar problem when running reports from PSSERVER. He initiates the report, >>>> it hangs, he kills it, then reruns and then it is OK. >>>> >>>> >It just appears like there is a "wakeup" issue going on when anyone initially access the SQLSRVR >>>> on PSSERVER. >>>> >>>> >>>> -- >>>> John W. Colby >>>> www.ColbyConsulting.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 >> > > >