What is the difference between the Rebuild Index and Reorganize Index Tasks? If I do one, do I need to do the other as well? For example, I plan on running a weekly maintenance plan that will do one or more of these tasks..
Check out http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx. The article is for 2000, but 2005 has the same basic principles (DBREINDEX = REBUILD and INDEXDEFRAG = REORGANIZE).
I am trying to create a simple Maintenance Plan using the Wizard to backup my databases. When I click finish everything works fine apart from the last step, "Saving Maintenance Plan". The report I get is this Maintenance Plan Wizard Progress - Creating maintenance plan "MaintenancePlan" (Success) - Adding tasks to the maintenance plan (Success) - Adding scheduling options (Success) - Adding reporting options (Success) - Saving maintenance plan "MaintenancePlan" (Error) Messages Saving maintenance plan failed.Although I haven't fixed the problem or found out which class it is looking for I have found that this is only happening on 1 workstation.
you will find the one which doesn't work. It stops your maintenance plan. Besides, you better setup your maintenance plan one by one, not an "all in one" package. as to why you are getting two messages is that the steps in the maintenance plan are not sequenced. In the maintenance plan editor, you need to drag the green arrow (go to next step on the blue arrow (go to next step on completion) and perform each step in the maintenance plan in sequence. If your jobs are not sequenced - those other steps are probably failing because Integrity Checks (DBCC CHECKDB) On Success: Rebuild/Reorganize Indexes On Success: Backup Database On Success: Maintenance Plan Cleanup Task Depending upon the system, I may include a step to Update Statistics and would include
Q303292 This is likely to be either a permissions problem or a sharing violation problem. The maintenance plan is run as a job, and jobs are run by the SQLServerAgent service. Permissions: 1 |Administrative tools|Services|SQLServerAgent|Startup). This account is the security context for jobs, and thus the maintenance plan. 2. If SQLServerAgent is started using LocalSystem (as opposed to a domain account) then skip step Anti-Virus software) having the backup file open at the time when the SQLServerAgent (i.e., the maintenance plan job) tried to delete it. 1. Download filemon and handle from www.sysinternals.com. 2 become very large, so it would be best to start it some short time before the maintenance plan starts. 3. Inspect the filemon log for another process that has that backup file open
easier for a new admin (or non-admin) to get themselves into trouble. - Does the maintenance plan wizard explain why transaction log backups are done, or what happens if they're not done? No - Does the maintenance plan wizard explain that "reorganizing" a database will generate a ton of transaction log activity? No - Does the maintenance plan wizard explain that shrinking a database will effectively "undo" the benefits of "reorganizing" a database? No - Does the maintenance plan wizard explain why repeated shrinking/growing of a database will lead to fragmentation and ultimately performance problems
1 week. The database backup files delete fine. However, the transaction backup files are not deleting. I tried recreating the maintenance plan to see if that would enforce the settings, thinking that there could be a setting corruption issue. However, this still 't delete ---- This is likely to be either a permissions problem or a sharing violation problem. The maintenance plan is run as a job, and jobs are run by the SQLServerAgent service. Permissions: 1. Determine the startup account for SQLServerAgent service (Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This account is the security context for jobs, and thus the maintenance plan. 2. If SQLServerAgent is started using LocalSystem (as opposed to a domain account) then skip step 3. 3. On that
week and I am examining the maintenance plans created by the person before me. They have one maintenance plan set do full backups AND tran log back ups once a week for 11 DB's. My question is this- Does that seem a bit much to put under one plan? Is there a good number (I would have thought only one per plan)that I can break this down to? I am witnessing some failures in the tranlog backup steps and want to isolate them. Thanks!Personally, I use maintenance plans ONLY for transaction log backups. For
Hi All, I am trying to create maintenance plan for updating statistics, checking database integrity and database backup, using wizard. First of all way to specify that (concering that I get IS package, very hard to modify anything)? More important question is regarding security issue with this wizard: I have only 'sa' access to the server missing something? Thanks in advance, Pedja P.S. The same thing would happen even if I created maintenance plan manually, because I would have to create connection objects manually (and specify 'sa' again) Pedja which is member of local administrators group. Version is 2005sp1. Why don't you try: create maintenance plan (updating statistics, integrity, ) logged on as 'sa', run it (successfully), change &
3 servers, ranging from 10MB to 100GB in size. I've had the same maintenance plans in place for at least a year, and I'm having some trouble now. In but now it seems my 3 largest databases (all 10GB or larger) are showing a failure in the maintenance plan history. The backups themselves are completing fine, though, and I did a test restore from them to confirm that. But the maintenance plan is returning the following errors: [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3013: [Microsoft][ODBC SQL Server Driver running under a Windows account with full permissions to the UNC. Also, all databases in question are set to FULL recovery mode. We are successfully doing transaction log backups
ok and reports correctly. Any ideas? KevHey Kev, (Don'cha hate it when no one replies to your question??) :-) Even though the History states failure, does the physical file actually get deleted, though? I've seen to SQL Server 'MHA-SQL01\SQL01' as 'MHACAREGROUP\CLU01SQLSVC' (trusted) Starting maintenance plan 'MHA CareG1_SITE Mtnce plan' on 19/03/2007  Database MHACareG1_SITE: Transaction Log Backup Destination: [G:\Program Files\Microsoft this db to a different folder with exactly the same details KevThat is interesting, not to mention odd. Question; What else does this Maint. Plan do besides the TLog backup? Database Backup, or an Optimization perhaps? Maybe it was one of those