Results 1 to 13 of 13

Access very slowed down on windows 10. Please Help

  1. #1
    kubachyl is offline Novice
    Windows 10 Access 2010 32bit
    Join Date
    Aug 2018
    Posts
    4

    Access very slowed down on windows 10. Please Help

    Hello
    I have Access 2010 application (.ade) linked to sql server by oledb. Many tables, forms, reports etc. It worked fine for many years. A few months ago my clinents start to report problems with performance. The program is working very slow (for example when I go to detailed form from list). It is always Windows 10 but not every PC. I think it has something to do with some windows update. Do You know the problem ? Is there any solution. I would be very grateful for your help
    Best regards


    KubaChyl

  2. #2
    ranman256's Avatar
    ranman256 is online now VIP
    Windows Vista Access 2010 32bit
    Join Date
    Apr 2014
    Location
    Kentucky
    Posts
    7,528
    Have you done compact/repair?

  3. #3
    kubachyl is offline Novice
    Windows 10 Access 2010 32bit
    Join Date
    Aug 2018
    Posts
    4
    Quote Originally Posted by ranman256 View Post
    Have you done compact/repair?
    Of course. Every time it goes to the client.

  4. #4
    ranman256's Avatar
    ranman256 is online now VIP
    Windows Vista Access 2010 32bit
    Join Date
    Apr 2014
    Location
    Kentucky
    Posts
    7,528
    Backend too?

  5. #5
    kubachyl is offline Novice
    Windows 10 Access 2010 32bit
    Join Date
    Aug 2018
    Posts
    4
    Quote Originally Posted by ranman256 View Post
    Backend too?
    As I mentioned Backend is in Sql Server.

  6. #6
    turbofish is offline Novice
    Windows 10 Access 2016
    Join Date
    Nov 2017
    Posts
    25
    What kind of SQL Server? 2012? 2014? 2016... Express? Standard, Enterprise?
    Any link servers? Replication?
    Any updates on the SQL side?
    Have you ran a trace on the SQL server during the slowness?
    Checked the error logs?
    Size of the database?
    Indexes?

  7. #7
    Ajax is offline VIP
    Windows 10 Access 2010 32bit
    Join Date
    Mar 2015
    Posts
    6,792
    Backend is in Sql Server.
    still needs to be compacted - at least the indexes need to be refreshed

  8. #8
    turbofish is offline Novice
    Windows 10 Access 2016
    Join Date
    Nov 2017
    Posts
    25
    Quote Originally Posted by Ajax View Post
    still needs to be compacted - at least the indexes need to be refreshed
    The indexes should be on the SQL server

  9. #9
    kubachyl is offline Novice
    Windows 10 Access 2010 32bit
    Join Date
    Aug 2018
    Posts
    4
    Hi

    Maybe I don't write it right. On this same server, this same time but diferent client computers - one with windows 7 - is ok, second windows 10 - not ok - very slow.
    So I think the indexes, version of sql, size.... have nothing to do with this.
    My question was rather - if You have some informations about windows 10 upgrades/patches that cause such a stituation and maybe solution.

  10. #10
    Ajax is offline VIP
    Windows 10 Access 2010 32bit
    Join Date
    Mar 2015
    Posts
    6,792
    The indexes should be on the SQL server
    I know that - perhaps it is not a factor in this case, but using sql server is not a create and forget operation. see this link

    https://docs.microsoft.com/en-us/sql...ql-server-2017

    take note of this paragraph

    The SQL Server Database Engine automatically modifies indexes whenever insert, update, or delete operations are made to the underlying data. Over time these modifications can cause the information in the index to become scattered in the database (fragmented). Fragmentation exists when indexes have pages in which the logical ordering, based on the key value, does not match the physical ordering inside the data file. Heavily fragmented indexes can degrade query performance and cause your application to respond slowly, especially scan operations.


    most sql server applications I have been involved with over the years require the indexes to be managed at least once a month - particularly those involved with tables with regular large data dumps.

    if You have some informations about windows 10 upgrades/patches that cause such a situation
    Sorry, not heard of anything - I'm running 2010 with SQL Server express and not experienced any degradation.

  11. #11
    turbofish is offline Novice
    Windows 10 Access 2016
    Join Date
    Nov 2017
    Posts
    25
    Not only indexes on the SQL server but statistics and wait stats to look at. If it is SQL 2016/2017, you can turn on Query Store to get more information on where the slowness is happening. You can also use the performance monitor on the server and machines to discover where the slowness is happening. Don't assume it is an OS issue [rare], there are a ton of other things to look at.

  12. #12
    AdrianG001 is offline Novice
    Windows 10 Access 2007
    Join Date
    Mar 2018
    Posts
    7
    If you are not using the SQL Native Client 11 try that to see if it helps.

    Regards,
    Adrian Gates
    SharePoint Admin - Apps4Rent

  13. #13
    NoellaG's Avatar
    NoellaG is online now Expert
    Windows 10 Access 2016
    Join Date
    Jun 2010
    Location
    Belgium
    Posts
    618
    Hi ladies and gents,

    if the slowness doesn't occur on every client at the same time, it's not the database server. If in doubt, just look at the standard reports -> Performance - top queries.
    The standard reports can also give you info regarding index usage. To check for slowest queries you can also use:

    SELECT TOP 50 query_stats.query_hash AS "Query Hash",
    SUM(query_stats.total_worker_time) / SUM(query_stats.execution_count) AS "Avg CPU Time",
    MIN(query_stats.statement_text) AS "Statement Text" , MIN( [creation_time]) as FirstIssuedOn, MAX( [last_execution_time]) as LastIssuedOn,
    SUM(query_stats.execution_count) as ExecutionCount
    FROM
    (SELECT QS.*,
    SUBSTRING(ST.text, (QS.statement_start_offset/2) + 1,
    ((CASE statement_end_offset
    WHEN -1 THEN DATALENGTH(ST.text)
    ELSE QS.statement_end_offset END
    - QS.statement_start_offset)/2) + 1) AS statement_text
    FROM sys.dm_exec_query_stats AS QS
    CROSS APPLY sys.dm_exec_sql_text(QS.sql_handle) as ST) as query_stats
    GROUP BY query_stats.query_hash
    ORDER BY 2 DESC;

    Regarding the index fragmentation: normally a weekly maintenance program runs a to take a full back-up and take care of the index maintenance (reorg or rebuild depending of the defragmentation). In case of a full recovery model the differential BU's are taken on a daily base and every 15 mins/hour the transaction logs . So on a normal system this shouldn't be a problem.

    When experiencing slowness, don't forget to check the connection object, maybe you need to install a new version. Another good and simple test: take a large Excel file and place it on the network. If it opens more slowly on the Windows 10 machines than the others, it could be network/OS related.

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Replies: 1
    Last Post: 05-11-2018, 09:11 AM
  2. Replies: 1
    Last Post: 02-23-2015, 06:06 AM
  3. Replies: 12
    Last Post: 02-09-2012, 01:27 PM
  4. Replies: 13
    Last Post: 07-18-2011, 09:05 AM
  5. Replies: 3
    Last Post: 07-15-2010, 04:53 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Tech Forums: Microsoft Office Forums