In recent months, our MP2 clients have been experiencing periodic freezing issues on the first day of the month. This occurs multiple times a day, lasting for 15-20 minutes each time. The problem affects clients using Windows 2003 Terminal Servers and Workstations, but the CPU, memory, and network usage on the Windows 2003 SQL 2005 server appear to be normal. Despite checking the Windows event viewer, no issues have been reported. We have several MP2 databases on the SQL server, with only one exhibiting this problem. Interestingly, users accessing other MP2 databases during the same period do not encounter any freezing. These databases are smaller in size and have fewer users. The last time this issue occurred, there were 15 connected users. We are seeking advice on troubleshooting this problem. Is there additional MP2 logging that can be activated for further investigation? The cause could be attributed to an overload of user activities or someone running a large report. Our setup includes SQL Server Edition Version 6.1 Build 20061031, Windows 2003 R2 SP2, and SQL 2005 SP3. Any insights are appreciated. Thank you, Cory.
Are you utilizing SQL Server 2005 Express or Professional? When the system freezes, what typically causes this issue? There have been instances where certain tables in the database had ownership corrupted, causing the system to lock up whenever a MP2 user tried to access them.
Our system operates on SQL 2005 Enterprise Edition (9.00.4053.00 SP3). I will consult with our system administrator to gather more information about the specific actions that have taken place. Thank you for your assistance. - Cory
Hello Jonathan, I wanted to update you on the activities that were being carried out when the clients experienced freezing issues recently. On Friday, one user was creating purchase requisitions and after the issue was resolved, he successfully completed 40 requisitions. This is the usual amount he handles twice a week. Around the same time, I was researching information in the Work Order History form for a specific equipment. Additionally, the tool cribs were conducting their weekly inventory cycle counts, which involves opening and printing a pre-existing report. Once the counting is done, they input the new stock levels into the system. Thank you for your attention to this matter. -Cory
Having a large amount of historical data can potentially lead to slow performance in the PR generation process. Conducting cycle counts and generating basic reports should not result in the MP2 program freezing up. How many years of historical data are you currently storing? Have you considered archiving older data to improve system efficiency?
I have been away from work recently, but I will conduct some research on the historical background. Thank you, Jonathan.
Hi Cory, considering the unique circumstances pointed out - that the freezing only occurs on the first day of the month and only impacts one database, the problem might be linked to some sort of monthly task that only targets this particular database. It might be a maintenance task, an automatic large report generation, or some form of scheduled extensive data processing. I would suggest scrutinizing the task scheduler on your SQL Server as well as the MP2 system itself since you mentioned you have several databases running without any problems. Also, even though you haven't noticed any event viewer entries linked to this issue, you might want to consider enabling SQL Server’s logging and flag potential warnings or errors on database level. It's equally essential to check if any third-party applications could be running tasks in the background potentially causing this issue. Overlooked scheduled tasks might be creating unexpected resource usage. Keep us posted.
Hi Cory, it's intriguing that the issue does not seem to correlate with any obvious factors like network usage or the size of the databases. One avenue you can explore is examining the tasks that specifically run on the first day of the month - possibly there are scheduled jobs or reports that might be causing this overload. Also, probing into whether certain actions are carried out by users exclusively on this MP2 database on the first day of the could be beneficial. Regarding additional MP2 logs, you might want to check out the MP2 system's diagnostic functions. It provides detailed activity records which might help isolate the cause. Lastly, just a suggestion, if feasible, backup and recreate this problematic database to check if it resolves the freezing issue.
Hey Cory, the fact that this issue is isolated to a specific database, which appears to be larger and with more users, suggests to me the root cause might indeed be related to high load activity or a large report as you mentioned. I'd recommend using SQL Profiler to troubleshoot this problem - it's great for tracking server activities and can monitor the workload applied to your SQL Server. This would help in identifying if a certain query or process is causing the freeze. If high load or a troublesome query isn't the issue, then it could be due to factors such as database fragmentation or outdated indices. Regular housekeeping tasks such as optimizing indices could help if the problem is due to these. Also, is your system up-to-date with patches? Sometimes, issues were resolved in later patches or updates. Good luck with your troubleshooting!
Hey Cory, it sounds like you're dealing with a complex issue! Since you’ve already ruled out the CPU and memory as potential culprits, it might be worth looking into the specific queries or reports being run on that problematic database. You could enable SQL Server Profiler temporarily to identify if there's a specific query that's causing the bottleneck. Sometimes, even a seemingly small report can pull a lot of data and cause performance hits, especially when multiple users access it simultaneously. Also, consider checking for any scheduled tasks or maintenance routines that might coincide with these freezing periods. Good luck!
Hi Cory, it sounds frustrating with those periodic freezing issues! Since it seems isolated to just one database, it could definitely be related to a specific query or report that's running at peak times. Have you considered enabling SQL Server Profiler to monitor the queries when the freezing occurs? This might help identify if there’s a particular operation or user activity causing the delay. Also, checking for blocked processes or deadlocks might provide some insight into what's happening during those times. It could also be worth consulting with your users to see if anyone is consistently running larger reports that coincide with the freezes. Good luck, and keep us posted on what you find!
Hi Cory, it sounds like you're dealing with a tricky issue! Since only one database is affected, it might be worth looking into any specific queries or reports that could be monopolizing resources for that particular database. Additionally, checking for locks or blocking can provide insights into whether a user is holding up processes when multiple users connect consistently. If you haven't already, enabling SQL Server Profiler during peak times could help you identify any unusual queries or transactions taking place. Finally, consider whether there are any scheduled jobs or backups coinciding with the freezing periods, as they could be impacting performance. Good luck troubleshooting!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: The cause of the freezing issues could be due to an overload of user activities or someone running a large report on the MP2 database.
Answer: Answer: To troubleshoot the slow response times, you can consider activating additional MP2 logging for further investigation. Additionally, monitoring user activities and reports being run during the freezing periods can help identify the root cause.
Answer: Answer: The freezing issues may be specific to a particular MP2 database due to its size, number of users, or the type of activities being performed on it. Smaller databases with fewer users may not encounter the same problems.
Answer: Answer: It is advisable to investigate the system resources on the SQL server hosting the MP2 databases, monitor user activities, and consider optimizing performance by identifying any resource-intensive processes or reports causing the slowdowns.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.