July 13, 2013 at 6:42 am
Hi All,
We have a huge load scheduled every day during that time we have no access / data for end user to access.
We need to plan this to remove the dependency between Load and usage.
The plan is to always Load data to a Load DB and Once Load is done, we need to swap out the Loaded to Current.
Please need your help to understand the steps and also the limitations on with this approach.
Sudhir Nune
July 13, 2013 at 1:23 pm
You could use database snapshot. Database snap shot will give a snapshot of your database at the point in time you create the snapshot. You can access the snapshot while the load is going on in the source DB. But be aware that creating snapshot will slow down your load. Your load might take a while longer than normal. As all the changed pages in the source database should be moved to the snapshot's sparse file. Once your load is done you can just drop the snapshot.
Also make sure that the snapshot's .ss file must be on a disk that has enough space. As the snapshot file will grow as the data will be loaded into the source database. If you are fine with these limitations snap shot is your best bet.
Once again this is only my opinion. You know what fits your environment the best.
July 16, 2013 at 3:44 pm
Can you please help me with a partition / File swap concept. please
July 16, 2013 at 10:06 pm
I do not think partition can server your purpose. Can you share some details here to see whether we have something to propose.
1. How much database size?
2. How much the Load volume will be ? In terms of Insert/update/Delete
3. How long the Load is running now?
Thanks
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply