Database deployment confusion

MattDWilliams

Hi looking at integrating TeamSite DCRs into an existing database schema and would like some advice on suggested approaches. The idea is to trigger the DB integration with the following WF; however any recommendations would be appreciated:

Workflow
----------------------------------
User - Creates/modifies a DCR
TeamSite - Triggers a review WF using tt_data

WF Task 1 (Deployment task) -
DCR deployed to Preview Environment Database.

WF Task 2 - (Group task)
Reviewer(s) - Takes task and Approves DCR in preview Environment.

WF Task 3 (Deployment task) -
DCR deployed to Prod Environment Database

Key points on the DB schema
-----------------------------------------
Heavy use of ManyToMany tables using unique auto-generated primary keys, e.g.

Documents
ID

Document_Content
ID | document_id(FK) | content_id(FK) | sort_order

Content
ID | Content


My Thoughts:
-------------------------------------

DAS - I have looked at DAS and from what I can see there is no way to restrict the trigger to Submits events only.

DataDeploy (Standalone, target side) - This seems the most intuitive moving files and DCRs.

Standard OD conf with custom DNR to populate the database.

Mr_Cruise

I think you are going down the right path with DD Standalone just three points:-

1. Starting a workflow for preview will be a big pain in the **** for the business. You may want to call a cgi on the save event that invokes the DD deployment. I personally hate starting workflows to preview content.
2. On one particular implementation the promotion to production required some additional data processing, which all needed to be transactional. So we created a stored procedure that moved the data into the production database.
3. You could use GUIDs instead of Database IDs and this may also help with moving data between environments.

Hope this helps

Lee