Ola hallengren SQL Server Index and Statistics Maintenance solution

We are using the Ola hallengren SQL Server Index and Statistics Maintenance solution from the past 6 months in our production system. Script is only used for Update Statistics not Index maintenance. Job used to take about 90-120 mins to complete which was completely normal considering the database size(1.8TB). All of a sudden the job started to take about 5-6hrs to complete from the past couple of weeks. We haven’t made any changes to the system. Each Statistics used to take less than 5 secs before now they take about 60-250 secs to complete. All this happened within a couple of days, not gradually. We are using SQL Server Enterprise edition.

Has anyone experienced this kind of issue before?
Any suggestions are greatly appreciated.

Below are the parameters used in SQL job.

EXECUTE dbo.IndexOptimize
–@Databases = ‘ALL_DATABASES’,
@Databases = ‘User DB’,
@FragmentationLow = NULL,
@FragmentationMedium = NULL,
@FragmentationHigh = NULL,
@UpdateStatistics = ‘ALL’,
@OnlyModifiedStatistics = ‘Y’,
@MAXDOP=2,
@Indexes=’ALL_INDEXES’,
@LogToTable=’Y’
–,@Indexes=’ALL_INDEXES,-%.dbo.eventhistory,-%.dbo.eventhistoryrgc’

Best Regards,
Arun

Info – Maintenance Break (Complete) | Forum Promotion

Code Forum Community

Modified Feb 27, 2021
Forum Promotion, meet Code Forum
Hello Forum Promotion, I would like to showcase the community that I built. I built Code Forum with intention of helping myself and others learn to code. Without the feeling that you are asking a stupid question and or even feel ashamed for…

Info – Maintenance Break (July 9th, 2021 – 11:59PM to 3:00AM EST) | Forum Promotion

Code Forum Community

Modified Feb 27, 2021
Forum Promotion, meet Code Forum
Hello Forum Promotion, I would like to showcase the community that I built. I built Code Forum with intention of helping myself and others learn to code. Without the feeling that you are asking a stupid question and or even feel ashamed for…

postgresql – Index maintenance on pg_catalog tables in AWS RDS

I have had some bad historical usage on my Aurora PostgreSQL instance. Namely, connections that create a lot of temporary objects and some very long running transactions (which limits autovacuum).

Now I have some very, very bloat pg_catalog indices.

For example: pg_attribute has only 34k records but pg_attribute_relid_attnam_index and pg_attribute_relid_attnum_index are 630MB and 450MB!

In total I have gigabytes of (bloated) system indices on system tables. However, I cannot REINDEX or VACUUM FULL these tables due to permissions.

Is this situation correctable in any way? Or is my RDS managed database permanently hosed and I need to migrate to a new one.

Coming Soon & Maintenance Mode PRO

Forget about complicated plugins that will waste hours of your time. We know you are busy and need quick results! Coming Soon is very easy to use, has only the features you need, and comes with themes that are right for your business.

2 million + free images. A great picture is not worth a thousand words. That’s why we’ve included over a million high quality free images to wow your visitors + Instagram-inspired filters!
170+…

.

support – How do I setup the fundamental architecture for field maintenance contracts with different number of service checkups

I’m looking for any assistance/help/advice in designing a simple application and database (Perhaps I should rather ask this question on a DBA Stack?). I need to create a simple application for a company that still makes use of a very basic Excel sheet to keep track of service and maintenance contracts, and when the next date is to perform preventative maintenance. As the sheet grows, it becomes unreadable, and very time consuming to pick out the elevators that require maintenance the coming month. The sheet doesn’t even make use of Excel functions etc. Everything is done by hand.

The company provides elevators. A client can have multiple elevators. Each elevator can have a different maintenance contract. For example elevator A requires two service check-ups per year, while elevator B only requires one check-up a year. A contract has a duration of one year, and can start any time of the year. After a year the contract automatically renews if the client doesn’t request to stop it.

Maintenance needs to be completed two months before the end of the contract. Example; Client John Doe signs a contract for two checks per contract year. The contract starts May 2021. May 2022 the next contract period starts. So the last maintenance check-up for the first period should be finished in the month of March 2022, and six months prior the first check-up should be done (September 2021). It is very important to keep track of the contract start and end dates because of invoicing etc.

Currently I’m thinking of a setup where we have a table contracts. This table contains the client_id (the one who pays). The user_id (the actual user of the lift). The elevator_id (details about the elevator), and a started_at date.

I made a quick draft with MS Access just for a graphical idea. The idea would then be to provide a date and the number of maintenance check-ups there should be in a form when creating a new contract and then automatically calculate the actual dates and create maintenance_visits rows for that contract (perhaps calling the table work_orders instead). When we near the end of the contract date and some of the work_orders' execution_date is still empty it would trigger some alerts. Same as when maintenance is coming up soon, looking at the planned_date field.

db design

I have a bit of programming knowledge but not that much experience. I hobby most of the time in my free time. I am the field engineer that have to do the elevator maintenance, meaning I am the one who use that Excel sheet the most, and it starts to annoy me a lot to try and figure out new routes for the coming week. So I thought of build something simple with Laravel so that I have a system that does the work for me and not me looking through a bunch of crazy colour coded Excel rows. The company is very small, they don’t want to buy already existing software that can help with this tasks. It is not feasible to invest in something that huge.

I hope there is somebody who would like to assist and show some samples or point out stuff that might be better if I do it completely different. Any advice and help to point me into the right direction will be very much appreciated!

maintenance – Camera once exposed to high temperature

maintenance – Camera once exposed to high temperature – Photography Stack Exchange

How can I render a specific node as the content for the maintenance page?

Use the Twig tweak module and create an overwrite template for maintenance-page.html.twig. Then copy & paste stuff from your base theme, but replace {{ page.content }} from the base theme with {{ drupal_entity('node', X) }}

E.g. for stable 9 theme this would look like

<header role="banner">
  {% if logo %}
    <a href="{{ front_page }}" title="{{ 'Home'|t }}" rel="home">
      <img src="{{ logo }}" alt="{{ 'Home'|t }}"/>
    </a>
  {% endif %}

  {% if site_name or site_slogan %}
    {% if site_name %}
      <h1>
        <a href="{{ front_page }}" title="{{ 'Home'|t }}" rel="home">{{ site_name }}</a>
      </h1>
    {% endif %}

    {% if site_slogan %}
      <div>{{ site_slogan }}</div>
    {% endif %}
  {% endif %}
</header>

<main role="main">
  {% if title %}
    <h1>{{ title }}</h1>
  {% endif %}

  {{ page.highlighted }}

  {# disabled {page.content} here #}
  {{ drupal_entity('node', X) }}
</main>

{% if page.sidebar_first %}
  <aside role="complementary">
    {{ page.sidebar_first }}
  </aside>
{% endif %}

{% if page.sidebar_second %}
  <aside role="complementary">
    {{ page.sidebar_second }}
  </aside>
{% endif %}

{% if page.footer %}
  <footer role="contentinfo">
    {{ page.footer }}
  </footer>
{% endif %}

sql server 2016 – Query store data maintenance background tasks

Query store has been running for years on the server without any noticeable disk IO spikes on log backups. We run on SQL Server 2016 EE version 13.0.5622.0

Recently we experienced a sudden surge in disk I/O every twenty minutes or so. We backup logs every five minutes, and every third or fourth backup would increase dramatically (from ~100 MB to >3 GB in size).

It happened at 2 AM without any changes being done to the server.

I dumped the contents of some of the log files and noticed a huge surge in swappages on the Query store system data tables when these log backup IO spikes occured. Disabling query store entirely caused the disk IO to resume at normal levels when backing up the log.

I presume the reason for the large transaction log backups would be online index rebuilds on the query store tables. We had configured query store to capture all transactions, auto cleanup, retain data for 180 days and max the data cache to 15 GB.

So far so good. I re-enabled query store after changing the configuration to auto, auto, 120 days and 8 GB, but now we are starting to see the same type of spikes in disk IO every 20 minutes or so when the transaction log is being backed up.

Have anyone had an experience like this and what did they do to fix the issue?

open source – Maintenance Activities and maintainability

Question 1

Assuming a project is started in as and Open Source project and is developing. Is dividing and labeling the maintenance activity is useful while maintaining the project?
-How it is useful for the contributes?
-How it is useful for who is using the project?
-How it is useful for someone who is looking for some opensource project to use?

Question 1

Assuming a project is started in an organization and is completed in given time and is according to its initial requirements. After the initial phase of completion the maintenance phase start.
Is dividing and labeling the maintenance activity is useful while maintaining the project for some one in side the organization?

Assuming all Maintenance activity belong to one of them

-Corrective maintenance
-Adaptive maintenance
-Perfective maintenance
-Preventive maintenance

Resource

ISO/IEC/IEEE International Standard for Software Engineering – Software Life Cycle Processes – Maintenance,” in ISO/IEC 14764:2006 (E) IEEE Std 14764-2006 Revision of IEEE
Std 1219-1998) , vol., no., pp.1-58, 1 Sept. 2006, doi: 10.1109/IEEESTD.2006.235774.

DreamProxies - Cheapest USA Elite Private Proxies 100 Private Proxies 200 Private Proxies 400 Private Proxies 1000 Private Proxies 2000 Private Proxies 5000 Private Proxies ExtraProxies.com - Buy Cheap Private Proxies Buy 50 Private Proxies Buy 100 Private Proxies Buy 200 Private Proxies Buy 500 Private Proxies Buy 1000 Private Proxies Buy 2000 Private Proxies ProxiesLive.com Proxies-free.com New Proxy Lists Every Day Proxies123.com Buy Cheap Private Proxies; Best Quality USA Private Proxies