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

db.r4 SQL Server costs incorrect #355

Open
paoloc0 opened this Issue Jul 18, 2018 · 5 comments

Comments

Projects
None yet
4 participants
@paoloc0
Copy link

paoloc0 commented Jul 18, 2018

Hi. As below, several SQL Server On Demand costs are incorrect, as compared to https://aws.amazon.com/rds/sqlserver/pricing/ :

screen shot 2018-07-18 at 16 41 28

Comparing the figures, it looks like the SQL Server On Demand cost is a mix of data from the various licensing options (Express/Web/Standard/Enterprise).

@paoloc0 paoloc0 changed the title db.r4.xlarge SQL Server costs incorrect db.r4 SQL Server costs incorrect Jul 18, 2018

@powdahound powdahound added the Bug label Jul 20, 2018

@DrMerlin

This comment has been minimized.

Copy link

DrMerlin commented Feb 11, 2019

++
It looks like all SQL Server costs are wrong. Also- not sure how the various options should be represented, with license or BYOL. Multi-zone, etc.

@cristim

This comment has been minimized.

Copy link
Collaborator

cristim commented Feb 12, 2019

Thanks for reporting this issue.

The RDS scraping logic where this would likely need to be investigated and hopefully fixed is available at https://github.com/powdahound/ec2instances.info/blob/master/rds.py

Looking forward to see a PR addressing this.

@paoloc0

This comment has been minimized.

Copy link
Author

paoloc0 commented Feb 12, 2019

@cristim It will no doubt take some effort to solve, given all the possible variations with licensing etc. A good improvement may be to simply let the viewer know that the information is incomplete, and give him some clue as to how it is incomplete.

@cristim

This comment has been minimized.

Copy link
Collaborator

cristim commented Feb 12, 2019

We could as well delete the RDS price information until someone is bothered enough to fix it.

@powdahound

This comment has been minimized.

Copy link
Owner

powdahound commented Feb 12, 2019

Perhaps this warning should return: 6f4ad8d

Related: #314, #198, and likely others. RDS has been a challenge for quite some time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.