|
I have created a staging table by making a copy of an existing table on my production database. I am going to do a reload to this table using reload script and dat file from another dump. No user will be accessing my staging table that I will be doing a load to, they do not even know if this table exist, will I be able to do a load to this table without affecting the production db which will be in heavy use while I am doing the load? does this make sense? |
|
Yes, you can do a load into your staging table on your production database without affecting your users too much. The only reason that your connected users may see any affect would be caused by the CPU and/or disk load that your LOAD TABLE command would be putting on your server. E.g if you are loading a very large table then the LOAD TABLE operation is going to do a lot of disk I/Os to read the dump file and (possibly) to write the new table pages to disk, and the extra I/O operations could slow down other operations on the computer if the disk cannot keep up with the I/O requests. 1
...so to be "nice" to your users, you could give your connection a lower priority in case you expect a noticable effect for them otherwise, such as SET TEMPORARY OPTION priority = 'Below Normal'; LOAD TABLE ...;
(11 Oct '12, 11:32)
Volker Barth
thank u all for their comments, do i set the below normal priority in my reload script
(11 Oct '12, 12:06)
javedrehman
Replies hidden
Yes, you can do so just before the LOAD TABLE.
(11 Oct '12, 12:33)
Volker Barth
|