Updated from 3.x to 4 - insufficient credentials error now

SQL Server performance monitoring and alerting

Moderators: Colin Millerchip, priyasinha, Adam, chriskelly

Updated from 3.x to 4 - insufficient credentials error now

Postby joshuawferguson » Fri Jan 10, 2014 4:36 pm

Since updating to SQL Monitor 4 I'm having trouble getting monitoring working again. As far as I can tell using Redgate's official documentation, I have the SQL account permissions set correctly, yet the log shows this:

The INSERT permission was denied on the object 'redgate_sqlmonitor_topqueries_b_lftcadsrv.(local)_redgate-sql', database 'tempdb', schema 'dbo'.


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.
joshuawferguson
 
Posts: 7
Joined: Wed Sep 11, 2013 10:24 pm
Location: Lafayette, LA

Postby Brian Donahue » Mon Jan 13, 2014 3:23 pm

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.
Brian Donahue
 
Posts: 6669
Joined: Mon Aug 23, 2004 10:48 am

Postby joshuawferguson » Mon Jan 13, 2014 3:32 pm

Thanks for the reply - are these permissions (db_datareader/writer) going to be reflected in the official documentation?
joshuawferguson
 
Posts: 7
Joined: Wed Sep 11, 2013 10:24 pm
Location: Lafayette, LA

Postby Brian Donahue » Fri Jan 17, 2014 1:08 pm

I've requested that this is included in future.
Brian Donahue
 
Posts: 6669
Joined: Mon Aug 23, 2004 10:48 am

Permanent table in tempdb??

Postby joshuawferguson » Tue Jan 28, 2014 5:48 pm

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. . .
joshuawferguson
 
Posts: 7
Joined: Wed Sep 11, 2013 10:24 pm
Location: Lafayette, LA

Postby thtwill » Thu Feb 13, 2014 6:01 pm

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.
thtwill
 
Posts: 3
Joined: Thu Sep 19, 2013 4:53 pm
Location: Manchester, NH US

Postby TheLonelyDBA » Tue Mar 11, 2014 8:41 pm

the same happens on the hosted beta of SQL Monitor: it tries to create "permanent" tables in TempDB.
Tips and thoughts on MS SQL, Oracle and MongoDB:
http://thelonelydba.wordpress.com
TheLonelyDBA
 
Posts: 18
Joined: Wed Oct 30, 2013 8:01 pm
Location: Brazil


Return to SQL Monitor 4

Who is online

Users browsing this forum: No registered users and 0 guests

cron