-
-
Notifications
You must be signed in to change notification settings - Fork 174
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
SQLwatch on RDS #483
Comments
Is this a duplicate of |
not really, my issue stems from the fact that sysadmin is not allowed and therefore I cannot run the PowerShell jobs, there is also not an option for a proxies available in RDS. We are migrating our workload to AWS and I am trying to establish if it is worth my while to pursue using SQLwatch as it has been working well for tests done for on prem |
Would you be interested in the Cloud version, im looking for businesses with AWS workload to make it compatible with RDS. |
Hi Marcin, possibly. Please share your email then we can chat "offline" about this. |
Would you like to go to https://sqlwatch.io/cloud/ and book a slot for a Zoom chat - so I can show you how it works and discuss details. Don't worry, its not going to be a sales pitch. |
Did you check DOCS to make sure there is no workaround?
https://sqlwatch.io/docs/
The Docs does not make specific mention of deploying to RDS. Can you please give me some guidance on how I can make SQLwatch work on RDS, I would love to help with the testing or assist with anything related to get this working as far as possible from my side.
Describe the bug
A clear and concise description of what the bug is.
There are several issues when deploying to and RDS instance because there are no sysadmin permissions like for instance creating an assembly on the master database
There is no option to create a proxy in RDS to enable a user to run PowerShell jobs
Manually deployed extended events because the default directory for extended events in RDS is different from the dacpac
To Reproduce
Steps to reproduce the behavior:
Occurs during testing of SQLWatch job execution and when trying to deploy dacpac
Expected behavior
A clear and concise description of what you expected to happen.
SQLwatch deployment fails with various errors but starting with an issue deploying to specific directory:
Error SQL72014: Core Microsoft SqlClient Data Provider: Msg 50000, Level 16, State 1, Procedure rds_extended_events_trigger, Line 172 Unable to create/alter extended events session: Extended events event_file target is allowed only to D:\rdsdbdata\Log
Error SQL72045: Script execution error. The executed script:
CREATE EVENT SESSION [SQLWATCH_blockers] ON SERVER
Screenshots
If applicable, add screenshots to help explain your problem.
Windows Server (please complete the following information):
SQL Server (please complete the following information):
SQL Server Management Studio (SSMS -> about -> copy info):
SQLWATCH version (from DACPAC or from sysinstances)
SQLWATCH 4.8.0.548 20230409190820
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: