July 8, 2016 at 3:31 am
Hi,
I appreciate this is quite a broad post.
I do not have admin rights in our SQL 2008 sandpit. I have only read/write.
What are the implications of this on tuning my queries/indexes etc. Are there any workarounds?
It is quite frustrating not being able to view things such as execution plans or the sys tables for missing index group...
Any suggestions welcomed.
Q
July 8, 2016 at 3:35 am
If the admin of the server won't increase your privileges, I think you have no choice but to set up your own instance on which you can do what you like. Next step - persuading them to share the code with you so you can recreate the environment for yourself!
John
July 8, 2016 at 3:44 am
Are there possibilities where they can extend rights within a specific database in the datawarehouse and/or is this all about how permissions are set up at the top level and flow down?
It is only one database i need to be able to check performance in.
Q
July 8, 2016 at 3:55 am
Awesome. Though i will be seeing flying pigs before i think i will be allowed to do this as it seems it can show sensitive information such as passwords. 🙁
July 8, 2016 at 3:58 am
quentin.harris (7/8/2016)
Awesome. Though i will be seeing flying pigs before i think i will be allowed to do this as it seems it can show sensitive information such as passwords. 🙁
Show passwords? Really? Or are you storing passwords in plain text?
Thomas Rushton
blog: https://thelonedba.wordpress.com
July 8, 2016 at 3:59 am
Only if the queries that are being run are rubbish enough to include passwords in them. But it comes down to this: they either trust you to do your job, or they don't.
John
July 8, 2016 at 4:04 am
True. It is a difficult place to be as a developer not sitting within the DBA/BI team but interfacing with their DW.
It seems to be a life of workarounds................................................................
July 8, 2016 at 4:08 am
@thomas-2 - This was in reference to a linked article which states that:
"Users who have SHOWPLAN, ALTER TRACE, or VIEW SERVER STATE permission can view queries that are captured in Showplan output. These queries may contain sensitive information such as passwords."
I have been trying to find a way that i can optimize/tune my queries where i don't have full admin rights.
Q
July 8, 2016 at 4:25 am
Yes, but that's only if queries contain such sensitive information as passwords. If no queries ever filter on plain text passwords (which they damn well shouldn't), then those can't expose plain text passwords.
To be honest, that warning's more relevant when giving those permissions to someone who doesn't already have read rights to all the tables.
Is this the production environment that you're trying to get access to, or a dev/test environment.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 11, 2016 at 11:46 am
To do any proper type of index tuning, you must have access to at least:
missing index stats, via sys.dm_db_missing* views;
index usage stats, via sys.dm_db_index_usage_stats;
index operational stats, via sys.dm_db_index_operational stats.
With that, you can do some tuning even without looking at the queries, although obviously if there are major coding issues in the queries, such as functions in WHERE conditions, you don't be able to find those using just index stats.
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
July 11, 2016 at 12:06 pm
quentin.harris (7/8/2016)
True. It is a difficult place to be as a developer not sitting within the DBA/BI team but interfacing with their DW.It seems to be a life of workarounds................................................................
Sometimes it is better to cut and run, blame sits somewhere!
...
July 11, 2016 at 12:21 pm
quentin.harris (7/8/2016)
Awesome. Though i will be seeing flying pigs before i think i will be allowed to do this as it seems it can show sensitive information such as passwords. 🙁
Neither execution plans, nor SQL Profiler traces, nor Extended Event traces show authentication credentials, unless they are embedded within the SQL select statement.
If your DBA doesn't want to grant you show execution plan permission in the same environment where there is a performance issue, then the DBA must be willing to accept that responsibility herself. Any DBA worth a damn knows basic performance monitoring and plan analysis even if she doesn't code T-SQL. If the DBA or management complains to you about a performance issue, tell them that without the proper tools and authborization needed to diagnose the problem where it occurs, all you can offer is your emotional support.
https://www.rickhanson.net/articles/making-a-family/support/
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
July 12, 2016 at 4:47 pm
HappyGeek (7/11/2016)
quentin.harris (7/8/2016)
True. It is a difficult place to be as a developer not sitting within the DBA/BI team but interfacing with their DW.It seems to be a life of workarounds................................................................
Sometimes it is better to cut and run, blame sits somewhere!
Heh.... First, get 3 envelopes...
http://wikibon.org/wiki/v/Prepare_three_envelopes
--Jeff Moden
Change is inevitable... Change for the better is not.
July 13, 2016 at 8:52 am
Jeff Moden (7/12/2016)
HappyGeek (7/11/2016)
quentin.harris (7/8/2016)
True. It is a difficult place to be as a developer not sitting within the DBA/BI team but interfacing with their DW.It seems to be a life of workarounds................................................................
Sometimes it is better to cut and run, blame sits somewhere!
Heh.... First, get 3 envelopes...
I recall one occasion when troubleshooting a stored procedure in production written by a developer who had recently quit. After I finally narrowing down the problem code block, the "comments" included some advice that was obviously an attempt at humor by a guy who had at the time of writing decided to move on to other things.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
Viewing 15 posts - 1 through 15 (of 15 total)
You must be logged in to reply to this topic. Login to reply