System Development Life Cycle

SQLServerCentral Article

Worst Practices - Objects Not Owned by DBO

  • Article

Last week Andy launched a new series about Worst Practices by talking about why the Hungarian naming convention is bad for column names. This week he's at it again, declaring that the practice of having objects owned by anyone other than dbo is BAD! Agree or disagree, we think you'll enjoy reading this article and adding your thoughts to the discussion!

4.86 (7)

You rated this post out of 5. Change rating

2019-08-01 (first published: )

38,287 reads

Blogs

The Community is YOU, Not Any Organization

By

As I type this, we’re leaving behind spring, and all the amazing events that...

Polyglot Persistence

By

I’ve seen the term polyglot persistence floating around Redgate a bit recently in the...

Six Months!

By

Oh good gosh. Six months without a single blog post. Most important information: I’m...

Read the latest Blogs

Forums

Dropping a Logon Trigger

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Dropping a Logon Trigger

SQL Injection Is Not Acceptable

By Steve Jones - SSC Editor

Comments posted to this topic are about the item SQL Injection Is Not Acceptable

Unzipping Word Documents in T-SQL

By cmartel 20772

Comments posted to this topic are about the item Unzipping Word Documents in T-SQL

Visit the forum

Question of the Day

Dropping a Logon Trigger

I created this trigger for testing on SQL Server 2022:

CREATE TRIGGER checksteve
ON ALL SERVER 
FOR LOGON  
AS  
BEGIN  
IF ORIGINAL_LOGIN()= N'ARISTOTLE\Steve'
 PRINT 'Steve logged in'
END;  
GO
Now I want to drop it. What do I run?

See possible answers