Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] [SQL Server Sink] the writer is very slow #7550

Closed
3 tasks done
RaymondFishWang opened this issue Sep 2, 2024 · 2 comments
Closed
3 tasks done

[Bug] [SQL Server Sink] the writer is very slow #7550

RaymondFishWang opened this issue Sep 2, 2024 · 2 comments

Comments

@RaymondFishWang
Copy link

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

I try sqlserver sink, the speed is very slow. The data volumn is 36w, if I use different source ,the result is the same. If i use mysql sink, we can load the whole data in 20s. And I watch the result table for sqlserver , we only insert 1k data into the table in 1s. It seems the batch size doesn't work. So the sqlserver sink has some problem .I also tried different jar lib.

SeaTunnel Version

2.3.5

SeaTunnel Config

sink {
    Jdbc {
        url = "jdbc:sqlserver://***:1433;DatabaseName=***;encrypt=false"
        driver = "com.microsoft.sqlserver.jdbc.SQLServerDriver"
        database="***"
        user = "****"
        password = "***"
        data_save_mode="DROP_DATA"
        schema_save_mode="ERROR_WHEN_SCHEMA_NOT_EXIST"
        generate_sink_sql = true
        batch_size = 200000
        table = "dbo.****"
        }
}

Running Command

/data/share_storage/seatunnel-2.3.5/bin/seatunnel.sh --config  **.config

Error Exception

no exception

Zeta or Flink or Spark Version

zeta

Java or Scala Version

1.8

Screenshots

image

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Copy link

github-actions bot commented Oct 3, 2024

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label Oct 3, 2024
Copy link

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant