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

Investigate possible perf issues in reverse engineering #4735

Closed
natemcmaster opened this issue Mar 9, 2016 · 1 comment
Closed

Investigate possible perf issues in reverse engineering #4735

natemcmaster opened this issue Mar 9, 2016 · 1 comment
Assignees
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Milestone

Comments

@natemcmaster
Copy link
Contributor

The SqlServer reverse engineering E2E tests tests occasionally fail with this error:

System.Data.SqlClient.SqlException : A transport-level error has occurred when
 receiving results from the server. (provider: Session Provider, error: 19 - Physical connection is not usable)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()

Could be

  1. Network issues
  2. Server dropped connection
  3. Server too busy

If its #3, it could be that we have perf issues in SqlServerDatabaseModelFactory.

@rowanmiller
Copy link
Contributor

We have done sanity testing that reverse engineer perf is ok with decent size databases. This is likely just a test issue.

@ajcvickers ajcvickers added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Projects
None yet
Development

No branches or pull requests

4 participants