-
Notifications
You must be signed in to change notification settings - Fork 22
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
50.000 limit on update query with join #470
Comments
Thanks for the information! The first query triggers legacy paging which limits the results to 50k. I'll look at improving this in the next update, but in the meantime you can work around it by forcing a calculation in the update account
set account.accountnumber = msdyn_customerasset.msdyn_name + ''
from account
inner join msdyn_customerasset ON account.accountid = msdyn_customerasset.msdyn_account |
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm experiencing a very strange behaviour. Maybe it's related to one of the latest updates (I'm using version 9.0.1) because I haven't noticed this before (and I've worked with big datasets in the past).
This query limits to 50.000 records (which is a pretty specific number/cap if you ask me):
whereas the following query has no limit:
To be clear, the dataset should update 57xxx records, which is the result of this query:
The text was updated successfully, but these errors were encountered: