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,311 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,311 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
48,016 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,852 reads
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Comments posted to this topic are about the item Spending Time in the Office
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers