Being Careful with Schema Ownership
When you create a schema, you might accidentally make yourself the owner, which can cause issues later. Learn how to ensure that your schemas aren't owned by transient employees.
2018-10-15
14,277 reads
When you create a schema, you might accidentally make yourself the owner, which can cause issues later. Learn how to ensure that your schemas aren't owned by transient employees.
2018-10-15
14,277 reads
If you have a schema you want to retire, here's a method for moving all objects inside that schema to a new one.
2018-09-25
47,903 reads
Have you ever wanted to know who made a schema change to your database? If so, that information is tracked in the default trace - Greg Larsen shows how to view it.
2017-03-28
6,381 reads
This is an expansion of the sys.schemas table.
User schemas are sorted to the top, schema type is decoded, schema authorization is included.
2015-07-14 (first published: 2015-06-10)
1,848 reads
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...
You kick off a distributed job expecting it to finish in minutes — but...
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