Codechef4u is a community for computer professionals,by computer professionals,just like you; who loves sharing and helping each others,Join them
Share your post

SQL server 2016 Transfer Maintenance Plan from One Server to Another

 Hi this is Vaibhav Shringi,This is my 3rd article on SQL server 2016 , in this article i will explain in detail how to transfer maintenance plan from one server to another.

In following example i used two server NMK135 and VS12345 for explanation and sample users Vadmin and nmk12345.

Transfer Maintenance Plan from One Server to Another

1. Connect to Source Integration server

Connect to Integration Services in SQL Server Management Studio (Where Maintenance plan already present Say SERVER-1)


2. Export Maintenance plan package from SERVER-1.

Connect with appropriate permissions and export the “DBMaintenancePlan” package.


3. Select Package Location as File System and browse for Package path to save “DBMaintenancePlan.dtsx” file.


4. Save and OK to compete export process in SERVER-1.

5. Transfer the newly exported file to new server file system (say SERVER-2).

6. Transfer “DBAdmin_RebuildIndexes” and “DBAdmin_UpdateStatistics” SPs from SERVER-1 to SERVER-2.

These SPs will be present in the database used for all DB admin related activity (Refer – DBCompareAdminDB ) and also checked-in in TFS.

7. Connect to Integration Services of SERVER-2. (use step 1). Import the previously exported package.


8. Connect to Database Engine of SERVER-2


9. Verify imported Maintenance Plan on SERVER-2.


10. Modify Plan to change some config entries.


11. Follow below steps ONLY IF WANT TO change Job Schedule Timing.

Click on Calendar button present right side of “Schedule” tab. Change appropriately and save the changes.


Below Step 12 to 14 are for “Nightly_DB_maintenance” Subplan.

Click on Nightly_DB_maintenance Subplan to see below screen.



12. Follow ONLY IF SPs are not Deployed (in step 6) in “DBCompareAdminDB” , say deployed in Database-1

   a) Double click on “VsriData – Rebuild Index” task.
        => Change “Use DBCompareAdminDB” to “Use <New Database Name>”
   b) Double click on “VsriData – Update Statistics” task.
        => Change “Use DBCompareAdminDB” to “Use <New Database Name>”


13. Verify Database Backup Location and database names.

      => Double click on “Full Backup Database task”.
      => Verify Folder location.


14. Verify Backup File Cleanup Period.

     => Double click on “CleanUp BackUp Files”.
     => Verify File Age. (Prefer to have 2 weeks) 


Below Step 15 is for “Every2Hrs_DB_Tran_Bkp” Subplan.

Click on Nightly_DB_maintenance Subplan to see below screen


15. Verify Transactional backup location and databases names.

      =>Double click on “Back Up Database Task”
      =>Verify Folder location. 



16. Save the Maintenance plan and close it. 

How to VERIFY Maintenance Plan Jobs?

VERIFY Maintenance Plan Jobs:

1. Open property window of both the jobs (right click on Job name)

  a. DBMaintenancePlan.Every2Hrs_DB_Tran_Bkp
  b. DBMaintenancePlan.Nightly_DB_Maintenance


2. Job owner:

    => If face any access related issue with Vadmin then change Job owner to “SA”.
    => We are facing this issue in VS12345 because of SQL agent service default configuration. 

3. Review Schedule Time etc.


धन्यवाद मित्रो !! 

Thanks Friends


SQL Server 2016 User Logins Management

This is my 2nd article on SQL server 2016, in this article I will explain in detail how to maintain user permissions or security.

SQL Server Security Management

A. Developers Access Control

It is very crucial to manage each user’s access rights as it can become hectic when need to manage 10-20 users with multiple permissions on their windows authentication.

To manage permissions among users, SQL has provided access management using windows groups.

Below are the steps to create any local windows group

1.  Search “Computer Management” and open it.
2.  Expand “Local Users and Groups” and then open Groups.

3.  Add new local windows user group and map windows users under it. Eg. “SQLUserGP_Read”, “SQLUserGP_Write” and “SQLUserGP_DBA”