Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

IPCC cra_db replication

We have IPCC 4.05.

We would like to write and test custom reports. I do not want to test the custom reports against the production server.

Can I replicate the database to another SQL server?

If so what db's need to be replicated?



  • Contact Center
Cisco Employee

Re: IPCC cra_db replication

I don't believe there is any supported replication to an offline or development database with UCCX. However, If you really want to build a development copy of the database, the safest and most non obtrusive way to get a copy of the production data is the use BCP.

BCP or "Bulk Copy Process" is a SQL 2000 utility that allows you to copy both table data & table formats into a flat file that can be loaded into another SQL 2000 database.

As far as the tables you probably want to grab most of the tables in the schema, approx 22 in all. This will ensure that the reports built in the "development" environment will work in the production environment.

As always when working with production data & systems take precaution to safe gaurd the data. i.e BARS Backup, Pull a drive, run BCP in off hours etc.

New Member

Re: IPCC cra_db replication

Thanks Dennis.

We only want to copy UCCX db and put in a location for testing. We may update it from time to time but not a daily thing.

Would doing a backup and then restore that backup to another SQL server work?

Or would using the BCP be the best way?



Cisco Employee

Re: IPCC cra_db replication

Back up and Restores are also an option. They can be a little tedious when not restoring to an exact copy of the SQL Database such as a development server .

BCP is just really clean and non obstrusive. If you really want to go the back up route, a faster option would be to just stop the DB, detach it through SQL, copy the DB & Log file, then reaatach the copys to a development SQL server and start it up.

This of course will require alittle bit of downtime as stopping the SQL Server will also stop CRS.