Scheduled Database Maintenance

I have a question that I'd like to post. Any assistance appreciated.
On each 2013 Database there is the scheduled maintenance and the 24x7. Does the scheduled maintenance run along with the 24x7 or is it a option of one or the other?

Scheduled Maintenance is deprecated in 2013. Its all workload based.
The background maint is really database checksumming.
This is for 2010, but applies for the most part:
http://blogs.technet.com/b/exchange/archive/2011/12/14/database-maintenance-in-exchange-2010.aspx
Bottom Line: I would leave the defaults as is. That makes Exchange happy.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Similar Messages

  • Database maintenance for sqlserver database to improve performance

    In our company sqlserver 2008 R2 is working as a project server database.
    I want to know commands for database maintenance.
    Please let me know all command in order which i need to run in sqlserver for database maintenance.
    because i want to increase performance of projectserver 2010.

    Hi John.Eddie,
    For increasing SQL Server performance, you can do full daily backup, transaction log backups, check database integrity, rebuild index and update statistics in database maintenance plan.
     However, you need to note that running "Shrink Database", it causes disk and as well as index fragmentation and leads to performance issues.
    To ensure your database stays healthy and available, there are a few "'must do" tasks. For example:
    1.Remove excessive transaction log file fragmentation.
    2.Set auto-growth correctly.
    3.Turn off any scheduled shrink operations.
    4.Turn on AUTO_CREATE_STATISTICS and AUTO_UPDATE_STATISTICS, plus have a regular process in place to update statistics.
    5.Have a regular process to run DBCC CHECKDB, take full database backups, plus differential and log backups for point-in-time recovery.
    For more information about database maintenance, you can review the following article.
    http://technet.microsoft.com/en-us/magazine/2008.08.database.aspx
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • SharePoint 2010 Database maintenance for beginners / developers

    Hey,
    here is a thing which I concern myself with from time to time.
    As a fulltime developer for SharePoint, I'm not quite familiar with maintaining it's databases. So after I set up my dev environment I usually don't care about maintaining the system. The logical consequence is that the system begins to slow down after a
    while.
    I don't have the time (and - to be honest - not the muse) to deep dive into the recommended maintaing plans by microsoft but I want to keep the performance of my system on an acceptable level. So I read the best practices provided by microsoft about index
    defragmentation, reorganizing, shrinking and so on but for me it's quite difficult to fully dive into these things without spending to much of my business time.
    So I wander if there are any execution-ready T-SQL scripts or something like that, which I can run from time to time to prevent my databases from to high fragmentation. I found some scripts for a stored procedure which reorganizes a particular index. But
    what I am thinking about is a script which iterates through all databases, all tables and all indexes and reorganizes them.
    I'm not looking for the perfect mainenance plan to achieve the best possible performance - I just want to prevent my dev environment from slowing down to much.
    Are there any scripts like that out there? or do you have other tips for me?
    Thank you!

    Hi,
    The steps to configure the maintenance plan is very easy and wont take more than 10 minutes. It is one time activity. It is nothing but drag and drag drop the required tasks from the Tool bar. You can schedule the maintenance plan to run on specific
    time or can run directly on demand basis.
    http://social.technet.microsoft.com/wiki/contents/articles/13956.sharepoint-2010-how-to-create-a-sql-server-2008-r2-maintence-plan-for-sharepoint.aspx 
    If you are looking only for SQL scripts then you may need to post in SQL forum, because maintenance plans will be almost similar for SharePoint Databases/or any SQL DBs.
    Please remember to mark your question as answered &Vote helpful, if this solves/helps your problem. ******************************************************************************************
    Best Regards,
    Pavan Kumar Sapara
    s p kumar

  • User receives meeting confirmation during Database Maintenance Window

    Hello
    I am facing an unusual behaviour which drives me crazy.
    A user (it’s unfortunately an important one) receives every night at 02:07 meeting confirmations in his “deleted items” folder. 
    During this time the Exchange Database Maintenance is scheduled. But I have no idea why this should generate such mails.
    I think somehow this maintenance Task sends out a meeting request which is automatically approved by the recipient and the confirmation is sent back to my users deleted item folder.
    Someone got an idea what is causing this?

    Hi,
    From your description, I would like to verify the following things for troubleshooting:
    1. Is this meeting a recurring meeting?
    2. I recommend you use message tracking to check who sent these specific emails.
    Here is an article about message tracking for your reference.
    Message Tracking
    http://technet.microsoft.com/en-us/library/bb124375(v=exchg.150).aspx
    Hope it helps.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • On demand database maintenance order

    Dear Experts,We have a prod database (databaseA)at 45GB and it contains tables for attachments(documents, images etc) from 7 companies/affiliates. The compressed full backup size is at 35.5 GB. We also maintain diff and trn backups that run on sched. We have fewer restore points due to storage constraint.A new database (databaseB) has been created in another server to house the other 6 companies' data, hence we can now delete other companies' data/records from this databaseA which leave it with only one company data. I think it is an occasion in which running DBCC shrinkdatabase would be legal so that the OS could reclaim the space.Sorry for that long overview, but my question is about the proper order of database maintenance. Is the following correct? Or will it create performance issues? Are each step necessary? Kindly enlighten me....
    This topic first appeared in the Spiceworks Community

    You can create a service order through sales order creation using action item of quality notification.
    Define the function module into action box's item in configuration
    SPRO > Quality Management > Quality Notifications > Notification Processing > Additional Notification Functions > Define Action Box > Define Functions for the Action Box
    SAP sample function module is 'QM06_FM_TASK_RMA_ORDER_CREATE' for creation of repair order.
    When you select the action item at quality notification, the pop-up screen to create a sales order will be shown.
    Also you can assign a service item(=service material) to create a service order at the same time.
    If you want to create a maintenance order(not service order), you have to use the maintenance notification.
    Because only maintenance notification can have the technical object like equipment, functional location.
    Regards
    Luke

  • Noticing a lot of database index fragmentation yet no Health Analyzer alerts...? Best practice for database maintenance in 2013?

    Could someone point me to a document for best practices for database maintenance with SharePoint 2013? I have read the 2010 document, but I'm hoping their is an updated one that I'm just missing.
    My problem is that our DBA recently noticed that many of our SharePoint databases have high index fragmentation.  I have the Health Analyzer rules enabled for index fragmentation and they run daily, but I've never received an alert despite the majority
    of our databases having greater than 40% fragmentation and some are even above 95%.  
    Obviously it has our attention now and we want to get this addressed.  My understanding (which I now fear is at best incomplete, more likely just plain wrong) was that a maintenance plan wasn't needed for index fragmentation in 2010/2013 like it was
    in 2007. 
    Thanks,
    Troy

    It depends. Here are the rules for that job:
    Sampled mode
    Page count >24 and avg fragmentation in percent >5
    Or
    Page count >8 avg page space used in percent < fill_factor * 0.9 (Fill Factor in SharePoint 2013 varies from 80 to 100 depending on the index, it is important not to adjust index fill factors)
    I have seen cases where the indexes are not automatically managed by the rule and require a manual defragmentation with a Full Scan, instead of Sampled. Once the Full Scan defrag completed, the timer job started handling the index fragmentation automatically.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • SQL 2000 Database Maintenance Plan drop downs for days, weeks, months, not displaying

    When setting up a SQL 2000 Database Maintenance Plan the drop down for Remove files older than is not populating with hours, days, weeks, or months. It is just blank. The version is  Microsoft SQL Server  2000 - 8.00.2039 (Intel X86)  
    May  3 2005 23:18:38   Copyright (c) 1988-2003 Microsoft Corporation  Desktop Engine on Windows NT 5.2 (Build 3790: Service Pack 2). Is there a fix for this issue?

    This also works. All the credit goes to a user named eyechart.  Great directions provided as well.
    http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=47575
    sqlmaint.exe
    was missing from MSDE 2000, but that was fixed in SP1 I think. Since this is SP3
    you probably have a missing registry value for the backup directory.
    I
    had to fix a similar problem last year on a bunch of laptops. They were all
    missing a registry value. Anyway, here is the fix:
    1. Fire up regedit and
    look under HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer
    2. Ensure you have
    a string value called BackupDirectory. The value for this should be the path to
    your backup dir. The default value is C:\Program Files\Microsoft SQL
    Server\MSSQL\BACKUP
    btw, this fix assumes you have a default instance
    installed. A named instance will have slightly different registry location and
    filesystem path.
    -ec
    Edited by -
    eyechart on 03/25/2005 21:04:27

  • Developing a Database maintenance plan

    Can you provide me links which goes into detail about developing a Database maintenance plan[i.e. taking backups [either Full or Inc] of DBs and transaction logs, deleting the oldest cycles, etcc]. I am not a DBA but at same time I am trying to learn as
    much as I can.

    Refer
    http://ola.hallengren.com/
    http://www.sqlservercentral.com/articles/Stairway+Series/72462/
    -Prashanth

  • Scheduling plant maintenance

    Hi
    I need for information about how to create or scheduling plant maintenance.
    Schedule preventive, predictive & corrective how can maintain in PM module.
    Ram Rathode

    Hi,
    In preventive maintenance scenario following are the things :-
    1) Creation of task list (for Equipment or Functional Location or General).
    2) Creation of maintenance plan (for Equipment or Functional Location or General).
    3) Attaching maintenance task list to the maintenance plan created.
    4) Scheduling of the maintenance plan for creation of maintenance orders (Call Objects).
    5) Maintenance/Breakdown order proceeding ( notification,planning,scheduling,execution,completion)
    There are following types of maintenance :
    1) Single cycle maintenance planning.
    2) Strategy plan ( Time based & Performance based )
    3) Condition based maintenance planning.
    4) Project based maintenance planning etc.
    Regards,
    TRB

  • Scheduled system maintenance on US data center - November 23rd 2014

    To ensure the highest levels of performance and reliability, we've scheduled a database server upgrade on our US data center. To minimize the customer impact, the upgrade is scheduled at the most convenient hours and will take up to 8 hours to complete. During the maintenance procedure, creating and updating content, Partner registration, trial site creation, publish from Muse, sFTP, APIs and some site admin sections will not be available. Additionally, during the 8 hours maintenance procedure, all sites on the US data center will experience 4 sessions of 15 minutes downtime. Except for the 4 scheduled  downtime sessions, the website front-ends will not be impacted by the maintenance.
    Maintenance schedule:
    Start date and time: Sunday, November 23rd, 3:00 AM EST (check data center times)
    Duration: We are targeting a 8 hours maintenance window
    Customer impact:
    Partner registration, Trial site creation, Adobe Muse publish, APIs, FTP and some admin section will not be available through the entire maintenance window on all data centers
    All websites and services on US data center will experience 4 sessions of 15 minutes downtime sometimes within the maintenance window
    Creating or updating content  on sites located on US data center will be unavailable during the maintenance procedure
    For up to date information about system status, check the Business Catalyst System Status page. We apologize for any inconvenience caused by these service interruptions. Please make sure that your customers and team members are made aware of these important updates.
    Thank you for your understanding and support,
    The Adobe Business Catalyst Team

    agents will be online for update from console.
    Method 1: Update the protection agents from the Data Protection Manager Administrator Console
    Open the Data Protection Manager Administrator Console.
    Click the Management tab, and then click the
    Agents tab.
    In the Protected Computer
    list, select a computer, and then click Update on the Action pane.
    Click Yes, and then click
    Update Agents.
    Note You may have to restart the computer after you install the agent upgrades.
    Method 2:Update the protection agents on the protected computers
    Obtain the update protection agent package from the following directory on the System Center 2012 R2 Data Protection Manager server: 
    <var>Data_Protection_Manager_installation_location</var>\DPM\DPM\Agents\RA\4.2.1217.0
    The installation packages are as follows:
    For x86-based updates: i386\1033\DPMAgentInstaller_KB2904687.exe
    For x64-based updates: amd64\1033\DPMAgentInstaller_kb2904687_AMD64.exe
    Run the appropriate DPMAgentInstaller.exe package on each protected computer, based on the architecture of the agent.
    Open the Data Protection Manager Administrator Console on the System Center 2012 R2 Data Protection Manager server.  
    Click the Management tab, and then click the
    Agents tab. Select the protected computers, update the information, and then verify that the agent version number is 4.2.1217.0
    Have a nice day !!!

  • Scheduled system maintenance on EU data center - October 26th, 2014

    To ensure the highest levels of performance and reliability, we've scheduled a database server upgrade on our EU data center. To minimize the customer impact, the upgrade is scheduled at the most convenient hours and will take up to 6 hours to complete. During the maintenance procedure, creating and updating content, Partner registration, trial site creation, publish from Muse, sFTP, APIs and some site admin sections will not be available. Additionally, all sites on the EU data center will experience a 20 minutes downtime sometimes during the maintenance window. Except for the scheduled 20 minutes downtime, the website front-ends will not be impacted by the maintenance.
    Maintenance schedule:
    Start date and time: Sunday, October 26th, 9:00 AM UTC (check data center times)
    Duration: We are targeting a 6 hours maintenance window
    Customer impact:
    Partner registration, Trial site creation Muse Publish, APIs, FTP and some admin section will not be available through the entire maintenance window on all data centers
    All websites and services on EU data center will experience a 20 minutes downtime sometimes within the maintenance window
    Creating or updating content  on sites located on EU data center will be unavailable during the maintenance procedure
    For up to date information about system status, check the Business Catalyst System Status page. We apologize for any inconvenience caused by these service interruptions. Please make sure that your customers and team members are made aware of these important updates.
    Thank you for your understanding and support,
    The Adobe Business Catalyst Team

    Congrats to Alan! Only one article, but it's a good one!
     System Center Technical Guru - October 2014  
    Alan do Nascimento Carlos
    ALM and IT Operations - Management 360 with System Center Operations Manager
    in 06 Steps
    Ed Price: "Lots of images. Great job breaking up the steps! Could benefit from a TOC and References. Great article!"
    GO: "Thanks for the only article. great btw. :-)"
    Ed Price, Azure & Power BI Customer Program Manager (Blog,
    Small Basic,
    Wiki Ninjas,
    Wiki)
    Answer an interesting question?
    Create a wiki article about it!

  • Scheduled system maintenance on US data center - March 15th 2015

    To ensure the highest levels of performance and reliability, we've scheduled a database server upgrade on our US data center. To minimize the customer impact, the upgrade is scheduled at the most convenient hours for the region and will take up to 6 hours to complete. During the maintenance procedure,  Partner registration, trial site creation, publish from Muse, sFTP, APIs and some site admin sections will not be available for sites on all data centers (including EU and AU). Additionally, during the 6 hours maintenance procedure, all sites on the US data center will experience 2 sessions of 1 minute downtime. Except for the 2 scheduled  downtime sessions, the website front-ends will not be impacted by the maintenance.
    Maintenance schedule:
    Start date and time: Sunday, March 15th, 6:00 AM UTC (check data center times)
    Duration: We are targeting a 6 hours maintenance window
    Customer impact:
    Partner registration, Trial site creation, Adobe Muse publish, APIs, FTP and some admin sections will not be available through the entire maintenance window on all data centers
    All websites and services on US data center will experience 2 sessions of 1 minute downtime sometimes within the maintenance window
    For up to date information about system status, check the Business Catalyst System Status page. We apologize for any inconvenience caused by these service interruptions. Please make sure that your customers and team members are made aware of these important updates.
    Thank you for your understanding and support,
    The Adobe Business Catalyst Team

    Congrats to Noah and Mr. X!
     System Center Technical Guru - March 2015  
    Noah Stahl
    Make System Center Orchestrator Text Faster than a Teenager using PowerShell
    and Twilio
    Ed Price: "Wow, I love the breakdown of sections. As Alan wrote in the comments, "Wow! Great article!""
    Mr X
    How to educate your users to regularly reboot their Windows computers
    Ed Price: "I love the table and use of code snippets and images! Great article!"
    Ed Price, Azure & Power BI Customer Program Manager (Blog,
    Small Basic,
    Wiki Ninjas,
    Wiki)
    Answer an interesting question?
    Create a wiki article about it!

  • Scheduled system maintenance on AU and EU data centers - March 8th 2015

    To ensure the highest levels of performance and reliability, we've scheduled a database server upgrade on our AU and EU data centers. To minimize the customer impact, the upgrade is scheduled at the most convenient hours for the regions and will take up to 6 hours to complete. During the maintenance procedure,  Partner registration, trial site creation, publish from Muse, sFTP, APIs and some site admin sections will not be available for sites on all data centers (including US). Additionally, during the 6 hours maintenance procedure, all sites on the AU and EU data centers will experience 2 sessions of 1 minute downtime. Except for the 2 scheduled  downtime sessions, the website front-ends will not be impacted by the maintenance.
    Maintenance schedule:
    Start date and time: Sunday, March 8th, 6:00 AM UTC (check data center times)
    Duration: We are targeting a 6 hours maintenance window
    Customer impact:
    Partner registration, Trial site creation, Adobe Muse publish, APIs, FTP and some admin sections will not be available through the entire maintenance window on all data centers
    All websites and services on AU and EU data centers will experience 2 sessions of 1 minute downtime sometimes within the maintenance window
    For up to date information about system status, check the Business Catalyst System Status page. We apologize for any inconvenience caused by these service interruptions. Please make sure that your customers and team members are made aware of these important updates.
    Thank you for your understanding and support,
    The Adobe Business Catalyst Team

    Congrats to Noah and Mr. X!
     System Center Technical Guru - March 2015  
    Noah Stahl
    Make System Center Orchestrator Text Faster than a Teenager using PowerShell
    and Twilio
    Ed Price: "Wow, I love the breakdown of sections. As Alan wrote in the comments, "Wow! Great article!""
    Mr X
    How to educate your users to regularly reboot their Windows computers
    Ed Price: "I love the table and use of code snippets and images! Great article!"
    Ed Price, Azure & Power BI Customer Program Manager (Blog,
    Small Basic,
    Wiki Ninjas,
    Wiki)
    Answer an interesting question?
    Create a wiki article about it!

  • Background Scheduling of Maintenance order for Calibration.

    Dear Experts,
    I want to scheule my calibration order in QM for calibration of Test Equipment in background.
    I have created my maintenance order for calibration of Gauges / Instruments (which are defined as Equipments). The dates for the calibration have been calculated based on time. When I go to the transaction of scheduling the order & save, the inspection lot for calibration is generated & the equipment task list is assigned to the lot.
    I want this to automatically happen in background. This is because I have thousands of equipments, for which I can not schedule the calibration manually.
    Regards,
    Prashant

    Hi,
    Please check below link if this can help it.
    http://help.sap.com/saphelp_scm2007/helpdata/en/c3/9e443cfb06e532e10000000a114084/content.htm
    Regards,
    Anil

  • Problem regarding scheduling of maintenance plan

    Dear Sap Gurus,
    I am facing the problem during the scheduling of maintenancepan thruough IP10 follwing error is coming
    "Planned date for maintenance plan 124 was scheduled for 00.00.0000"
    Planned date for maintenance plan 124 was scheduled for 00.00.0000
    Message no. IP889
    Diagnosis
    During scheduling of the maintenance plan, the planned date was set to 00.00.0000.
    This error can occur, if, for example, the cycle for the planned schedule is too big (offset) means that the planned date is actually after the 31.12.9999.
    Procedure
    Check the master data of the maintenance plan to ensure that no date is calculated after the 31.12.9999.
    If necessary, check the counters used and the annual performance.
    I explore all the things in SPRO also also check the setting parameter for the plan but i didnt get any breakthrough for my above problem.Plz guide me whats the exactly problem with scheduling of of maintenance plan.
    points are sure
    Regards
    Rakesh

    Summary
    Symptom:
    In the scheduling of a multiple counter plan, the system
    1. generates message IP889 "Planned date for maintenance plan &1 was scheduled for 00.00.0000" or
    2. terminates with CONVT_NO_NUMBER.
    Other terms
    Scheduling, IP10, IP30, maintenance plan scheduling, maintenance plan, multiple counter, BADI IPRM_MCP_SCHE_CHANGE, CONVT_NO_NUMBER, SAPLIWP2, LIWP2F19, MCP_PREPARE_RESCH_CALLED_CALLS, LV_ABNUM
    Reason and Prerequisites
    This problem is caused by a program error.
    Solution:
    Implement the attached source code corrections.

Maybe you are looking for