Skip to Content

Very long export time for table VBRP


I am trying to increase # of datafiles for my SQL DB of an ERP system.

It is about 10 TB.

I am using heteregenous system copy method and tried to export my system.

I used attached split_input.txt file for table splitting. When I was preparing this I divided table sizes to 4 GB pieces.

Table splitting took about 8 hours.

Export time took in 2.5 days.

I run TimeAnalyzer and got attached "export_time.txt" result file.

When I examine the export times of tables, I see that there are 23 hours lasting VBRP table split exports.

The other tables mostly exported in less than 2-3 hours. Even the biggest MSEG table.

Why could VBRP table take too much time to export?

Is there a way to accelerate VBRP table export time?

Can you help, please?



Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Aug 18, 2016 at 07:52 AM

    Hello Yuksel,

    I don't quite follow why you would be performing a heterogeneous copy to increase # of datafiles but I guess you have your reasons. I'm not a SQL Server person.

    If you could provide info on a couple of things.

    1. The R3ta split log files

    2. Confirm you used the standard R3ta_hints file

    3. There was no cpu or i/o contention during the export

    4. Provide a explain plan of the select statement from the VBRP WHR file

    5. Check you have a index that properly supports the select statement from (4)

    When I'm splitting tables I work to two criteria, size and number of entries in the table. I've found on quite a few occasions that size splitting isn't always the most optimal so if the table in question is huge (entries not size) I split into packages of between 5-10 million entries.

    Just taking Oracle as an example, having too many splits and split packages running in parallel actually ends up slowing the export down as you get read contention.

    Will wait for your reply before we look into this deeper.



    Add a comment
    10|10000 characters needed characters exceeded

    • Hello Amerjit,

      We were using virtual system for test purposes.

      We moved the system to a more powerful physical system.

      And also I applied below notes.

      1054852 - Recommendations for migrations using Microsoft SQL Server

      1241751 - SQL Server minimal logging extensions

      On that system we exported all tables in 20 hours.


      Yuksel AKCINAR

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.