Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
Learn2010
Starting Member
12 Posts |
Posted - 2014-07-15 : 11:10:16
|
I developed an Access database. An outside vendor was called in to create a SQL back-end. Now that person is gone. (That is the only Access database with a SQL back-end.) Since then, all my Access databases are extremely slow and sometimes don't even want to close. I have several other Access databases with back-ends on a very large network. Other users of those databases do not have the same problem I am having. Can anyone help me with this? I tried an Access forum and got no replies. So, I assume it is a SQL problem.Thank you. |
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2014-07-15 : 12:39:15
|
I would try updating statistics on all of the tables, doing at least a 25% scan. How big are your tables?Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
|
|
gbritton
Master Smack Fu Yak Hacker
2780 Posts |
Posted - 2014-07-15 : 12:47:06
|
1. Did the vendor give any warranty for the work? (If they broke it, they should fix it!)2. Was performance acceptable just after the vendor was finished? (Did the vendor leave things running well?)3. How long after the vendor's contract did the performance problems begin? (or was it immediate?)4. Has the volume of work pushed through Access to SQL Server grown substantially? (Maybe your server is running out of horsepower)5. What changes were made to the server or your network after the vendor left? (problem could be in many places)6. Do you have an in-house DBA who looks after your SQL Servers? (The GO-TO person in your company for SQL Server problems)7. Do you have regular re-indexing jobs in place?fyi many organizations use a setup like yours for parts of their businesses. SQL Server itself would not likely cause performance problems unless horribly configured or vastly underpowered (RAM, CPU) or not actively maintained (e.g. index rebuilds) |
|
|
|
|
|