You’re offline. This is a read only version of the page.
Announcements
54
We were using SL 2011 with the remote desktop to access 2011 SL , later we upgraded it to 2015 SL, our allocation process has gone from 5 minutes to over 120 minutes, when we run allocations on new SL 2015 from client. What might be causing the issue?
*This post is locked for comments
Breaking down the setup into separate components makes troubleshooting much easier. If you have an SL demo database, you can run an allocation there to look for environment vs. program changes vs. the upgraded database being the issue. Reviewing and testing each part separately helps greatly in narrowing down what is causing a large difference in performance.
That is puzzling. Is it only with allocations that you noticed a big change after the upgrade?
I assume you have done the simple things like checking that the server that SQL Server runs on isn't short of disk space and checked the Event Logs and SQL Logs for errors. And be sure to check the same things on the remote desktop you are using.
At this point I would do one of two things:
When something slows down like that the first thing I try is rebuilding the indexes in SQL Server.
Maybe you don't have enough RAM in your SQL Server. If your server is virtualized it is easy enough to increase the RAM to see if it makes a difference. But I would do the indexes first.
#1
André Arnaud de Cal...
294,206
Super User 2025 Season 1
#2
Martin Dráb
232,968
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
