Hi, I have created a new management agent as SQL2 in the synchronization manager and already have a management agent SQL1 ,adma and Fimma. SQL1 is for database table tb1 and SQL2 is for database table tb2.Data is provisioned from table tb1 to others using run cycles. When I run the run profiles then the existing data are not provisioned to the new database table tb2 whereas if I insert a new data then that data is provisioned to the new table. Example: Table tb1 already have 250 data. Now I have added a new data 251.The record 251 is provisioned to table tb2 but the existing 250 data are not provisioned to tb2. Regards, Anil

Have you run a full synchronization on your SQL1 management agent since you put the provisioning in place? And are you using classic provisioning using a metaverse extension or declarative provisioning with synchronization rules defined in the portal? Chris

hi, Thank's for response Yes, first i run full synchronization on our SQL1 Management agent then only new data and updated is provisioned not existing is provisioned in new SQL2 Mangement and we are using declarative provisioning with synchronization rule that is defined in the portal. regards Anil kumar