November 19, 2013 at 8:45 am
Ok, this is a question I've so far not seen a clear & cut answer for.
I got the following situation on the production server of our client
Databases for each application,only containing views referring to a set of databases with the data in them (the closest I can reveal is that the data comes from sensors on industrial machinery)
Now they want to 'pump' over the data to test/dev enviroment so that the application testers & devs can toy with concurrent data.
So atm their is a fairly over extensive procedure running, there's 2 major flaws with it
1)It takes long to 'pump' the data over
2)It doesn't see the diffrence between what we want to sent to test and what we want to send to dev,we might have a solution tomorrow for this.
Now back to the question,if I use a replication on the views: What data do they show.
The one on the live or the one from the test/dev
And is that data physically on the live/dev
I thank you for your time
November 19, 2013 at 9:17 am
If you replicate views or stored procedures, you are replicating the object definition, not data.
It will display only what is in the local DB (assuming you have all the dependant objects).
November 19, 2013 at 4:18 pm
OK,this is I feared then.
The problem is that I'm not allowed to put on replication on the databases that actually contain the data,its both to business sensitive and volatile (and with volatile I mean the data in those databases can change on a minute to minute basis).
November 20, 2013 at 1:06 am
Can you replicate the data to a different database and modify the view to access cross-database?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply