SQL Standard Maintenance plan .. small business applications

Hi all just completed a migration to SQL 2016.     The server hosts a handful of databases for a small company.    The largest database being 13 Gig in size.    The business is primarily Monday to Friday 8-5 for database usage.       I know maintenance plans are different for every environment.      I would just like to know if what I am doing is enough.    And often enough.     I am confident in my backup plan but not the maintenance.

I am running a single maintenance plans as follows once a week after hours.

Check Database Integrity on all user databases default settings
Rebuild Indexes on all user databases default settings
Update Statistics on all user databases default settings

Thanks in advance
LVL 2
Zoldy2000Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ste5anSenior DeveloperCommented:
You should set up these alerts as e-mail notifications:

Capture.PNG
I'm often doing index rebuilds only on weekends. Normal databases don't change that much. But run reorg and update statistics in the night.

Also take a look at Brent Ozar's sp_Blitz.
0
Zoldy2000Author Commented:
To clarify you are suggesting I run reorg and update statistics daily instead?   Then run the rebuild once on the weekend on its own?     Can you explain what configuring those alerts does for me.
0
ste5anSenior DeveloperCommented:
Those alerts mark all serious problems, either hardware, OS or SQL Server. Thus they normally need immediate reaction.


Severity Level

Meaning

17 Insufficient Resources
18 Nonfatal Internal Error Detected
19 SQL Server Error in Resource
20 SQL Server Fatal Error in Current Process
21 SQL Server Fatal Error in Database (dbid) Process
22 SQL Server Fatal Error Table Integrity Suspect
23 SQL Server Fatal Error: Database Integrity Suspect
24 Hardware Error
25 (no description)

see also Database Engine Error Severities.

A index rebuilt requires simply more resources. An in many databases the index fragmentation does not grow over a day significantly. Thus it's often sufficient. But your doubts are right, this a rule of thumb. So take a look at index fragmentation over time.

An index reorg is faster. And a daily statistics update done daily is often needed, when having faster changing data.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Zoldy2000Author Commented:
thank you
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SQL

From novice to tech pro — start learning today.