Comments
7 comments
-
Hello,
I've never seen SQL Monitor 3.x try to write to tempdb, so it must be part of the new performance analysis in v4. Most users would have the ability to write to tempdb as it's used implicitly by SQL Server as storage space for joins and other things. Thanks for pointing that out. -
Thanks for the reply - are these permissions (db_datareader/writer) going to be reflected in the official documentation?
-
I've requested that this is included in future.
-
I know this is a bit after the fact, but I found (on another server) that if sqlmonitor's login doesn't have ddl_admin rights on tempdb, it also fails. By default (without this ddl_admin right) the login should be capable of creating temporary tables (with the # prefix) in tempdb. Why is sqlmonitor trying to create permanent tables in tempdb? Seems very counter intuitive. . .
-
Thanks for this topic, it helped me too. I encountered this same issue on a fresh install of version 4.
I agree, this was not mentioned in the official documentation page (http://documentation.red-gate.com/display/SM4/Requirements) at time of this post. -
the same happens on the hosted beta of SQL Monitor: it tries to create "permanent" tables in TempDB.
-
Hello all,
I know it's quite a bit after the fact, but for anyone reading I wanted to mention the documentation has now been updated to include the need for db_datareader and db_datawriter on tempdb.
Kind regards,
Alex
Add comment
Please sign in to leave a comment.
I added db_datareader and db_datawriter permissions to the account, and monitoring resumed fine. Is there something I'm missing that may have caused this error? Thanks.