OS Memory high

Question

Post reply

OS Memory high

Admingod

SSCertifiable

Points: 5997
More actions
July 31, 2019 at 5:44 pm

#3667657

OS Paging is high and i could see that the root cause from task manage and it show ssis execution process consuming highest memory. The jobs are running using SSIDB Catalog, This started since the application upgrade and the upgrade has created some database schema in the back end. Do you think this spike would be temporarily for all the jobs running for the first time.Any advise how this could be fixed or the cause would be upgrade or anything you can think of? However, i noticed maintenance jobs ran longer than normal because of upgrade. Please advise? Thanks in advance.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Phil Parkin SSC Guru Points: 246961 More actions · Answer 1

the upgrade has created some database schema in the back end

Please explain what you mean by this. A new database schema should not do anything bad, per se.

The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin

Admingod SSCertifiable Points: 5997 More actions · Answer 2

Can you think of anything that could cause the problem?

Jeff Moden SSC Guru Points: 1004356 More actions · Answer 3

Admingod wrote:

Can you think of anything that could cause the problem?

Call the vendor that provided the "application". If the "application" was written by you good folks, you can't "call the vendor". 😀

Whether or not a 3rd party vendor is involved, you've got some digging to do... I'm assuming by "the upgrade has created some database schema in the back end" that you mean new objects, indexes, procs, etc. Without knowing what changed, it's not possible to even speculate beyond the notion that someone wrote some "crap code on a poorly designed database".

My recommendation is to download a copy of Adam Machanic's "sp_WhoIsActive" and start digging.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Grant Fritchey SSC Guru Points: 398882 More actions · Answer 4

The same as with any performance problem, you have to gather metrics to identify where the issues lie. I can't tell you what the problem is because other than high memory use (and SQL Server always uses all the memory you give it), you've haven't supplied any metrics. Gather query run times and wait stats. Follow where the data leads you.

I'm with Jeff, get in touch with whoever upgraded whatever software we're talking about.

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning