Hi @Coreysan ,Welcome to Microsoft Q&A,
First of all, we can't reproduce your problem, so we can only make wild guesses.
Your service may inadvertently create a situation that causes resource exhaustion or deadlock on Server2. Even if you don't see any immediate errors, long-running transactions, blocking, or locking in SQL Server may accumulate over time and eventually overwhelm the server and cause it to crash.
If the operation of your service or other processes causes excessive writes or growth to the TempDB database (used for temporary data storage in SQL Server), this can eventually cause the server to crash when space is exhausted or fragmentation becomes severe.
Check the TempDB configuration and look for any rapid growth in file size. Ensure that there is enough disk space and consider setting up an alert for TempDB size growth.
While the service itself might not show any errors, SQL Server logs or Windows Event Viewer on Server2 might provide clues about what happens before the crash. Look for any critical errors, warnings, or unusual behavior in the logs.
Best Regards,
Jiale
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.