Hi Dhiviya,

 please apply below step 3  from out system documentation.

https://success.outsystems.com/support/enterprise_customers/maintenance_and_operations/multiple_database_catalogs_and_schemas/

For SQL Server

Moving a module to a different database catalog

To move a module to a different Catalog execute the following steps:

1. Backup the source and destination databases

2. Mark the module to be moved.

   1. Open Service Center.

   2. Open the edit screen of the module, select the Operation tab, and in the Catalog drop down select the Catalog where the module is to be moved to.

   3. Click Apply.

      The module won't be moved right away but marked for to be moved, therefore, it will still be operating with its old Catalog.

3. Copy the database data.

   For Version 8 or lowerFor Platform 9 or higher

   a. Once the module is marked to be moved, go to the module details screen, click the Download Data Copy Script link to download the script that will copy the module data.	a. Once the module is marked to be moved, take offline the application that contains the module (using the Take Offline button, on the application details screen).
   b. Bring the application that contains the module offline using the Take Offline button, on the application details screen.	b. Create a SQL script to copy the module data to the destination catalog (run it in SQL Server Management Studio).
   c. Run the script in SQL Server Management Studio, to copy the module data. You must have the same privileges as the admin user of the Platform.	c. Ensure that the move operation was successful and the application is working properly.
   d. The script creates the source tables and views into the destination Catalog, copies their data, and creates the constraints.
   e. Ensure that the move operation was successful and the application is working properly.
   f. In the source Catalog, tables are kept for any eventual data recovery situation, but are renamed with an OLD_ prefix. To definitely delete them, use the commented (not executed) SQL commands at the end of the script.
   g. In case of moving large amounts of data, require the DBA assistance to examine data copy steps on the script, and possibly make them more efficient.

4. Finish the module move

   1. In Service Center, publish the module.

   2. The Platform Server first checks that all tables of the module are created in the destination Catalog. Then it displays a Use Matching Tables option that is to be selected, and continue with the publishing process.

   3. If the module has Consumer modules, republish them, or build a solution with all referenced modules and publish it in a single step.

   4. Bring the module online using the Bring Online button on the module details screen.

   5. The module is now using the new Catalog.

thanks

cv