search

opserver / Opserver

Stack Exchange's Monitoring System
https://opserver.github.io/Opserver/
MIT License
4.51k stars 827 forks source link

Amazon RDS: 'active' #143

Open win32nipuh opened 8 years ago

win32nipuh commented 8 years ago

The problem is that Amazon RDS does not allow to create objects in master database.

Oh no!

sp_WhoIsActive was not found or was not accessible on this SQL instance.
Please visit Adam Machanic's site to grab the latest copy.
NickCraver commented 8 years ago

I'm not sure this is worth solving, it depends if it's possible first.

If you install sp_WhoIsActive in your database, does it work? If Amazon RDS is this limiting, it's likely that the procedure can't even access the system-level information it needs to function either.

win32nipuh commented 8 years ago

I have created sp_WhoIsActive in my database, then ran it:

EXEC sp_WhoIsActive 
    @show_sleeping_spids = 2, 
    @show_system_spids = 1, 
    @show_own_spid = 1

It seems it works ok, it displays processes in my db, master db.

VictoriaD commented 8 years ago

I've put sp_whoIsActive in a different database to master. Once I changed the Initial catalog in the connection in SQLSettings.json to point at that database instead of master, it seems to work OK. I haven't done extensive testing, just poked about a bit, but happy so far. This could be an option for you.

NickCraver commented 8 years ago

@win32nipuh can you confirm this as an option? When I get to much needed (tons of) documentation, I can include some pointers there.

win32nipuh commented 8 years ago

Ok. Can I do anything to help to solve this issue? Btw, in my app I try to detect where it is connected: RDS or normal SQL Server. Depending on it the app has different behavior.