1 Answer
- Newest
- Most votes
- Most comments
0
Hello and thank you for taking time to post a question on re:Post.
When you are using a managed database option like Relational Database Service (RDS), you change database configuration settings with Parameter Groups.
If you are getting that error due to an query timeout, you may want to look into changing some Parameter Group settings.
- First create a Parameter Group with your chosen SQL Server engine.
- Find the Parameter Group you created, and begin to modifying it by clicking Edit parameters.
- Search for the option
remote query timeoutand change the setting to a desired time. Setting it to0will turn off any timeout which may help your setup temporarily.
Please review this documentation for more information on settings.
answered 10 months ago
Relevant content
- asked 10 months ago
AWS OFFICIALUpdated 10 months ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated a year ago
Thank you for your reply however the remote query timeout parameter group setting appears to have no affect on the ExternalCommandTimeout Sql Server Analysis Services server property. I've set it to 0 and 54000 in the parameter group and are still getting the same errors when attempting to process the SSAS Cube. Please see https://learn.microsoft.com/en-us/analysis-services/server-properties/general-properties?view=asallproducts-allversions for more info regarding the SSAS properties.
@SeanGreen I would then believe the only way you could do this is running an RDS Custom SQL Server instance. There are not many low level configurations you can change when running a managed instance, but you may have luck with RDS Customer SQL Server. You can try changing the msmdsrv config file. If that does not work for you, you can also place a PFR to the AWS team.