Share via

SQL - Performing Operation

Xolani 1 Reputation point
2020-12-04T11:14:09.65+00:00

45164-capture.png

Please assist, its been doing this for the past 30mins
I have restarted the machine twice now and to no avail

SQL Server | Other

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Cengiz YILMAZ 1 Reputation point MVP
    2020-12-04T11:19:22.867+00:00

    Do you have the necessary free space on your drives?

  2. CathyJi-MSFT 22,406 Reputation points Microsoft External Staff
    2020-12-07T06:50:11.427+00:00

    Hi @Xolani ,

    What is your SQL server version? Using select @@version to check it. What is the version of SSMS? Suggest you using the latest version SSMS 18.7.1.

    Please check your steps from this document to found if you missing something.
    Get started with this simple example of the Import and Export Wizard

    You can also using other methods to import data from Excel to SQL server, such as SSIS package. Please refer to MS document Import data from Excel to SQL Server or Azure SQL Database to get more information.

    Best regards,
    Cathy

    If the response is helpful, please click "Accept Answer" and upvote it

    0 comments
  3. Ronen Ariely 15,216 Reputation points
    2020-12-07T11:11:09.857+00:00

    Good day,

    Monitoring during the import on your SQL Server side

    Note: * Before you start, you will probably want to reset the aggregated statistics using DBCC SQLPERF.

    (1) Check for write Latency using sys.dm_io_virtual_file_stats
    (2) Check for Wait Statistics, Latches, and Spinlocks (for example using sys.dm_os_wait_stats;)
    Note: This doc can help you understand the result you get.
    Note: check for page splitting on the way.
    (3) Check the Activity monitor using SSMS

    Indexes issues

    There is a good chance that you indexes and mostly the clustered index cause the issue. You import data which is inserted in the middle of the existing data and led to page splitting and other un-wanted result.

    Import the data to a staging table first (Heap table without indexes and and empty table without any data). Next copy the data to your final table.

    Check the size limitation of the transaction file in the database.

    Make sure that the max size is not blocking you and the transaction file has free space for the action so it will not need to growth during the task.

    Check that your tempdb is not the bottlenecking in the process

    Check the size of the database, monitor the activity

    Try to use direct approach

    Create the table manually using queries and import the data using INSERT from OPENROWSET from the excel

    You can also export the data for flat file csv and use BULK IMPORT

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.