nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Recent Upgrade to 10.1.1, now getting SQL problems, DB unloads.

ACDII

Getting more and more frequent memory pressure errors in SQL, something it never did before until the upgrade.

Event Type:    Information
Event Source:    MSSQLSERVER
Event Category:    (2)
Event ID:    10311
Date:        12/29/2010
Time:        5:27:53 AM
User:        N/A
Computer:    ORIONDB
Description:
AppDomain 45 (NetPerfMon.dbo[runtime].44) is marked for unload due to memory pressure.

For more information, see Help and Support Center at go.microsoft.com/.../events.asp.
Data:
0000: 47 28 00 00 0a 00 00 00   G(......
0008: 08 00 00 00 4f 00 52 00   ....O.R.
0010: 49 00 4f 00 4e 00 44 00   I.O.N.D.
0018: 42 00 00 00 00 00 00 00   B.......

Not sure what I can do to resolve it, but when the DB gets unloaded, we can no longer access the Orion interface, and it is starting to happen more often. The link in the event log is of no help either.

Find more posts tagged with

Accepted answers

All comments

mcbridea

Just to be sure, did you also apply the 2 applicable hot fixes? If not, apply those and see if that helps. If you have applied them please open a ticket.

ACDII

Thats a good question. I have a current ticket opened due to them forgetting to add the ability to run off a drive other than C:, which makes me wonder if they applied the hotfixes after reinstalling the app several times.

MarieB

Hi ACDII--

Can you clarify how this affects your other post where you mention the ability to run off a drive other than C. Here's the link to expedite:

Thx,

ACDII

unrelated to the drive installation problem, just something that cropped up after the install. I know during the install tht SQL was modified in some way, whether that modification is what is causing the memory issues now, I dont know. For all I know, MS SQL could just be doing what MS does best, work when it wants to.