Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Favorites |
infavorites:mine infavorites:1234 |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
In the context of a database, maintenance describes routine operational tasks around a database system, such as monitoring, tuning and backup procedures.
5
votes
I can't think of any benefits, but I am also biased towards using my own jobs for maintenance.
I think that MPs are very good for new or accidental DBAs, as they allow for some maintenance …
answered May 6 '11 by SQLRockstar
6
votes
Shrinking the database will allow for you to give back some space to the O/S, but that space comes at a performance cost as the shrink activity fragments the database. You can fix this by rebuilding y …
answered Apr 6 '11 by SQLRockstar
12
votes
PARTNER OFF
If you are concerned that your maintenance will take a long time, then you should perform regular transaction log backups, so as to make certain the log does not grow out of control and …
answered Mar 21 '11 by SQLRockstar
2
votes
Use sp_start_job.
Put that command into a job step as needed. No need to worry about the duration of previous jobs.
answered Oct 31 '13 by SQLRockstar
0
votes
I'd advocate for you doing native, compressed, backups to Azure blob storage and using SQL Server managed backup. But the business may require you to store them locally.
Just remember that you pay f …
answered Mar 8 '17 by SQLRockstar