Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2004-10-21 : 08:30:32
|
| Daljeet singh writes "Hi, i am working on the development of a data warehouse tool as a windows application in VB.NET, that will be storing atmost 3 PRODUCTION databases. The senerio is as follows : 1. I cant' do any type of alteration to my source database.2. My source database don't have a change log Mechanism i.e if any change is made to the production database means if a field value changes in any table, mysource database don't have a way to see the previous values, so we are suppose to develop a tool that keeps track of data-history means keeps the log of changes made to database at FIELD LEVEL each time the synchronization is run, and also keeps the copy of the procduction database.2. My source database are all in Microsoft SqlServer, and the destination database i.e our app. database will also be in again in Microsoft SqlServer.3. Technology currently we are planning to use is again Microsoft VB.Net.4. Also we have to strongly consider the fact the data storing / retrival should be fast. Also the amount of data being avail. in the source databases is really huge as with in 5 months of bussiness one of our source database has got increased to 850 MB.So you are requested to suggest me the Best way out to replicate the database's and maintain the history at field level. Through a windows application.ThanksDaljeet" |
|
|
|
|
|
Field level Database replication.