I'll preface this question with the fact I know about This question but unfortunately it was no help to me as "don't run the database over the network" is just not an option.
Last week we migrated our file server from Server 2000 to a Server 2008 R2 Standard x64 Virtual Machine. We have a database that provides contact information for stakeholders and business partners. This is a proprietary database written in house by our database analyst. Since we migrated the server, this database has been running much slower than normal.
That said, I've been looking for the cause for the past week as this is an important database for us. We are moving toward using another system, but I'd like this issue resolved with this sooner rather than later.
Relevant Information
Linked tables have been re-linked to reflect their new UNC address and the database compacted
There is currently no anti-virus running on the server
All client anti-viruses are set to not scan network drives
We have made an antivirus exception for msaccess.exe for testing purposes with no luck
I tried dropping the firewall on the file server with no luck
I haven't noticed any issues with file access (in fact, most of my employees have said they've noticed an increase)
I would love to hear any suggestions as to why people would think that Server 2008 R2 is slowing down the database.