Post reply

Import stops after 97k rows

  • September 7, 2011 at 3:32 am

    #247587

    I've been trying to upload a text file with 117,000 records into a database table using the Import & Export wizard. I have tried field lengths field but it seems that it always stops at row 97,423. The file looks OK, nothing unusual in the text. Any reason why it would stop like this?

  • September 7, 2011 at 5:36 am

    #1377894

    Please have a look on the t-log usage. Verify that u got any t-log full error, if so follow these methods to overcome

    1. Increase the t-log space

    2. If AUTOGROWTH is not enabled, try with enabling it

    1. Change recovery model to BULK LOGGED and try to run the transcation, change it back to original RECOVERY MODEL, take a full backup

    SQLforU
    info@sqlforu.com
    For online training on SQL Server and Sybase, please contact
    contact@sqlforu.com
    www.sqlforu.com

  • September 7, 2011 at 9:35 am

    #1378063

    SQLforU (9/7/2011)

    Please have a look on the t-log usage. Verify that u got any t-log full error, if so follow these methods to overcome

    1. Increase the t-log space

    2. If AUTOGROWTH is not enabled, try with enabling it

    1. Change recovery model to BULK LOGGED and try to run the transcation, change it back to original RECOVERY MODEL, take a full backup

    I have tried to increase the log file size and set unrestricted growth using the following code, but there's a bug in it somewhere:

    USE master;

    GO

    ALTER DATABASE dataease2

    MODIFY FILE

    (NAME = dataease2_log,

    SIZE = 110MB,

    FILEGROWTH=10MB

    MAXSIZE = UNLIMITED)

    GO

  • September 7, 2011 at 9:37 am

    #1378064

    Add a comma before MAXSIZE

  • September 7, 2011 at 9:46 am

    #1378072

    Please keep an eye on DISK free space as well.

    Keep the MB growth to higher values somewhat like 100MB. Which will make sure that it creates less number of VLFs

    SQLforU
    info@sqlforu.com
    For online training on SQL Server and Sybase, please contact
    contact@sqlforu.com
    www.sqlforu.com

  • September 7, 2011 at 9:57 am

    #1378080

    Ninja's_RGR'us (9/7/2011)

    Add a comma before MAXSIZE

    The command runs ok, but when I check properties it still says "restricted growth"

  • September 7, 2011 at 10:02 am

    #1378088

    Are you sure you are looking at the right file? Did you refresh after running the command?

  • September 7, 2011 at 10:15 am

    #1378103

    Ninja's_RGR'us (9/7/2011)

    Are you sure you are looking at the right file? Did you refresh after running the command?

    Yes - I know because the size change to whatever I set in the statement. But the growth is still set to restricted growth.

  • September 7, 2011 at 10:19 am

    #1378108

    Restricted to what?

  • September 7, 2011 at 10:31 am

    #1378117

    If I look at the properties, it says "autogrowth by 20MB, restricted growth to 2Gig"

  • September 7, 2011 at 10:33 am

    #1378120

    Change it there and hit ok.

  • September 7, 2011 at 10:35 am

    #1378121

    I can do that but it will not save. (Is this because it's the Express version?)

  • September 7, 2011 at 10:37 am

    #1378124

    Possibly, would make sense.

  • September 7, 2011 at 10:41 am

    #1378125

    Here is the error message from the Import/export wizard log:

    The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.

    And no matter what size I set the logfile to, it seems to break down at record 97342

  • September 7, 2011 at 10:44 am

    #1378129

    Can you stop it at 97K and see how big the db is? That would confirm the express limitation theory.

Viewing 15 posts - 1 through 15 (of 17 total)

You must be logged in to reply to this topic. Login to reply