Click here to Skip to main content
15,880,651 members

Comments by Menci Lucio (Top 24 by date)

Menci Lucio 23-Feb-24 3:38am View    
That machine has three SQL instances. The first is the default installation and contains only the master database. The other two instances each hold only the ERP database, one for production and one for testing.

There is nothing else. My sensations say that there is something works bad in that machine. I asked for that.

FOR ALL WHO READ UNTIL HERE. There might be a misunderstanding. When I talk about "test," I do not refer to developer testing. Our supplier has its own developer and test environments. We, while developing the customization, have our own developer and test environments. We put the application (often, when required) in a fifth environment to permit third parties to test their development when an external connection is required. Finally, the sixth and seventh environments are the production and user testing environments (where customer employees can test and learn how to use new capabilities). These are the two environments present in the production machine, what I have called until now "production" and "test".
Menci Lucio 22-Feb-24 12:27pm View    
We have dozen of customers that has the same configuration. The customer that has the little DB space (some of them has over 150Gb of DB, one of them is over 200Gb, this one has 11 Gb) and uses less the server (it makes about 10 invoices at a day, some other customers has the same work per minute, it uses only few barnches of the applications on the DB, the others uses much more). All other customers works well in both test and production (that are in the same machine but in different sandboxes, and stress test on test machine doesn't impact in the production one). Why has this customer problems on test memory space if all the other that stress much more the memory and cpu usage haven't if the pressure memory detection works properly? What is that make you figure out that are so secure that memory pressure detection works properly? Do you saw some reports?
Menci Lucio 22-Feb-24 12:13pm View    
No. SQL Server IS DESIGNED to free memory up. From the link I posted (https://learn.microsoft.com/en-us/sql/relational-databases/memory-management-architecture-guide?view=sql-server-ver16#memory-pressure-detection):
"The Resource Monitor task monitors the state of external and internal memory indicators. [...] Memory brokers monitor the demand consumption of memory by each component and [..,] it calculates and optimal value of memory for each of these components. [...] This information is then broadcast to each of the components, which grow or shrink their usage as required."
Menci Lucio 22-Feb-24 10:52am View    
I think the focus of the problem is not properly centered. Let me correct the question
Menci Lucio 22-Feb-24 9:25am View    
Right observations, but not the right answer. It seems that Memory pressure detection[^] doesn't seems to work properly in that server. I don't know how to monitor it and change its behaviour.