SQL Server running extremely slowly.

One of my clients has a large Access application running against a SQL Server BE (2012) which has been running along smoothly until last Thursday, when reads and writes from/to the SQL server slowed significantly, and are resulting in ODBC timeout errors when writing to various tables.

The client rebooted the server over the weekend, but the problem persists.
All of the various services (SQL Server, agent, browser, reporting services) appear to be running.

Just looking for any input from those of you with extensive SQL Server experience on where to look in the Windows or SQL Server logs to see if I can figure out what is going on?
LVL 51
Dale FyeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

als315Commented:
Look at hdd problems (failed disk in raid, etc), general performance (cpu and memory usage)
0
lcohanDatabase AnalystCommented:
What version/edition of SQL is running? You could use SQL own "Performance Dashboard Reports" - they are great! - to debug all kind of real time issues in SQL Sever.

https://www.microsoft.com/en-ca/download/details.aspx?id=29063

Also, was there any change before " last Thursday, when reads and writes from/to the SQL server slowed significantly" on the Access application side OR on the SQL Server? Patching, etc? Any new software installed or updated - antivirus in particular?
0
candideSoftware developerCommented:
what often happens: check if tempdb is on HDD volume C:\ and C:\ runs out of space
0
Dale FyeAuthor Commented:
I was able to resolve the problem by creating a new copy of the table which was causing the problems with the write process.  I then copied all of the record data into that table, had 3 records not copy over for some reason, but was able to identify and view those records to get most of the data into the new table.

After pointing my application at this new table, everything is running smoothly again.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.