Hi

I've been trying to think of how to manage changes between our staging server and production on a current project.

The problem is that the documents are going to be worked on regularly by up to 100 users. There are 100 gb of files that I am planning to import into DMX.

The plan is roughly this:

1> Test DMX on staging to make sure it does what everyone wants
2> Install DMX on the PROD server.
3> Take the current document location (which is a file system) offline for a weekend
4> Import all the documents into DMX on PROD server.

Then I would have to sync the PROD dnn database back to staging to get all the DMX data. Configure DMX on the staging server to point to the same respository if this is not done by the DB sync.

The problem we have is that thereafter we need to be able to sync the staging site across to PROD on a regular basis to provide the latest versions of custom modules were are building. But, if we do this then we need to skip the DMX tables from the sync. And we also have the issue that documents from PROD are available on staging which we don't really want.

How does everyone else do this kind of thing? What is the recommended method?

Any comments and suggestions would be really helpful.

Gus

Hi Peter,

We have the Exact same requirement. Is there an easy way to export all Documents and attributes (in DB) from one DNN instance to another?

Thanks,
Chhavi

@Gus: I don't really have any additional suggestions.

@Chhavi: There is no way to do this. The reason is that data in DMX is linked to User and Role IDs as well as Portal and Module IDs. Between two installations, even if you create the same pages, modules, users and roles, these IDs can be different. This means there is no safe way to relate to the context in another portal/DNN installation.

Peter