Web database problems

[warren]

My companies website is updated by the use of ASP web forms writing to a database using ADO. We want to change it so updates have to be authorised before they go live.

We took a copy of the db as a staging database and pointed the web forms at that and planned to replicate accross using SQL procedures. With a 'modified' bit field which produced a page displaying new and modified data and an 'authorised' bit field which alowed transfer to the main database (set up as a linked server from the staging database)

Transfer of data is using an update trigger

We have run into a few problems ;-)

1. BLOB fields (text) will not transfer accross (binary data is not written to the 'inserted' table)

2. A couple of tables are updated by site visitors so data integrity problems arise between the two databases

Anybody have any ideas?

[khuyen]

A couple of questions:

What is the minimum tolerable latency between your staging data and your production data?

Is there an admin to review the staging content prior to authorizing its availablity on the production database?

-Khuyen


------------
warren at 4/4/00 9:10:16 AM

My companies website is updated by the use of ASP web forms writing to a database using ADO. We want to change it so updates have to be authorised before they go live.

We took a copy of the db as a staging database and pointed the web forms at that and planned to replicate accross using SQL procedures. With a 'modified' bit field which produced a page displaying new and modified data and an 'authorised' bit field which alowed transfer to the main database (set up as a linked server from the staging database)

Transfer of data is using an update trigger

We have run into a few problems ;-)

1. BLOB fields (text) will not transfer accross (binary data is not written to the 'inserted' table)

2. A couple of tables are updated by site visitors so data integrity problems arise between the two databases

Anybody have any ideas?