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

Provide way to reconnect to database #252

Closed
DBojsen opened this issue Jan 25, 2019 · 2 comments
Closed

Provide way to reconnect to database #252

DBojsen opened this issue Jan 25, 2019 · 2 comments

Comments

@DBojsen
Copy link
Collaborator

DBojsen commented Jan 25, 2019

If I open from database to do direct changes and testing, and my network becomes unstable - I am not able to save back to the database.
My only option is to deploy, save to file/folder (and later deploy) or loose my changes.
It would be very nice to be able to reconnect and save the changes to the database.

@otykier
Copy link
Collaborator

otykier commented Jan 25, 2019

Yeah, this is a known issue, which in my experience is especially prevalent when working with Azure Analysis Services. I have plans to run a background thread which will try to keep the connection alive on regular intervals, but there’s always a chance that the connection could be lost altogether.

Since I’m using the TOM to load the model metadata from a server, I’m not sure there’s any way to recover a lost connection. Doing a full deployment and reloading the model seems to be the only workaround. Unfortunately, this is not exactly the same operation as calling the TOM Model.SaveChanges() method, which is what happens whenever you click the save button, which is why I prefer that users manually do a deployment in that case (for example, you’d have to manually reapply Power Query credentials after each deployment - this is not necessary when calling Model.SaveChanges()).

@otykier
Copy link
Collaborator

otykier commented Apr 24, 2019

2.8.2 now automatically reconnects every minute in the background, to keep the connection alive and refresh the auth token. Let me know if you're still experiencing any issues with this.

@otykier otykier closed this as completed Apr 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants