2015-12-21
326 reads
2015-12-21
326 reads
Louis Davidson explains why a little database courtesy goes a long way.
2015-11-16
232 reads
Whose fault is it if a database is hacked and its contents appear on a hacker’s site? Louis Davidson suggests that, regardless of limitations, the DBA always bears some responsibility.
2014-12-22
163 reads
2014-11-24
167 reads
In opera, tragedy or absurdity happens because the characters are incapable of standing back, and making a difficult decision. Instead, at every stage, they just drift towards their fate by taking the easy option. Don't let the same fate befall you, as a DBA.
2014-08-04
119 reads
Louis Davidson on why DBAs ought to do one thing, every day, that is scary.
2014-07-07
236 reads
As a professional, our knowledge of a given task should extend, at a minimum, one level deeper than is strictly necessary to perform the task. Anything deeper can be left to the ridiculously smart, or obsessive, or both
2014-05-12
125 reads
Louis Davidson on the small dreams that DBAs can nurture, each day, to elevate the drudgery of a seemingly banal task into a celebration of purpose.
2014-03-03
176 reads
Like Sherlock Holmes, a DBA needs the sound deductive reasoning to pinpoint the root cause of a crime, in amongst a thousand interesting but irrelevant details.
2013-11-18
139 reads
Technical debt is frustrating but dealing with it requires patience. Louis Davidson explains why.
2013-09-02
142 reads
Running AI and data pipelines on the edge instead of the cloud has gone...
By Steve Jones
While writing another post I realized my UNION query didn’t work as one might...
It’s time for T-SQL Tuesday again! And we’re almost to number 200! T-SQL Tuesday...
Comments posted to this topic are about the item Secure Cached Plans
Comments posted to this topic are about the item Complex Data Processing with dbt...
Comments posted to this topic are about the item Over or Under Provisioned
The DMV, sys.dm_exec_cached_plans, contains rows for each cached plan on an instance. In Azure SQL Database, not every used has rights to every database, as there does exist an instance behind each database. How is security handled for this DMV in Azure?
See possible answers