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,519 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,519 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,714 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,887 reads
By James Serra
(This is the third post in a three-part series on how AI is changing...
Continuing with my takeaways from SQLCon and FabCon Europe in Barcelona, let’s talk about...
By Steve Jones
Next year the PASS Data Community Summit is in DENVER! and London, but Denver...
Comments posted to this topic are about the item Pay for Performance, which is...
Telp/Wa 628218200233 Jl. Jend. Ahmad Yani No.118, Sidakaya Dua, Sidakaya, Kec. Cilacap Sel., Kabupaten...
Comments posted to this topic are about the item Helping an English Student with...
I have a table, dbo.bittest, where I am testing an application response. This has this structure:
CREATE TABLE [dbo].[BitTest] ( [insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()), [a] [bit] NULL ) ON [PRIMARY] GOMy application runs this code:
INSERT dbo.BitTest
(
insertdate,
a
)
VALUES
(DEFAULT, 'true')
GO
See possible answers