Phil Factor

  • Interests: Motorbikes, Beer, gardening, conservation, Local history.

SQLServerCentral Editorial

Programming Rules and 'Best Practices' Can't Replace Professional Judgement

In which Phil Factor casts doubts on 'programming policies'. For certain, any IT team development requires plenty of methods of working that maximise productivity, but coding standards and ‘best practices’ have to be treated with caution. Programming rules can’t replace professional judgement

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(7)

You rated this post out of 5. Change rating

2015-02-09

216 reads

SQLServerCentral Article

Static Code Analysis: a necessary irritation.

There is little doubt that static code analysis can contribute to code quality and deliverability. As an aid to a developer, it seems increasingly essential, but can it ever deliver reliable metrics of code-quality? One shudders at the potential misuse of quality metrics in the wrong hands. My hope is that it remains just an aid to human judgement; and creativity.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(1)

You rated this post out of 5. Change rating

2014-07-28

112 reads

Blogs

SSMS Is Getting Smarter—and This Isn’t Just About Writing SQL

By

Continuing with my takeaways from SQLCon and FabCon Europe in Barcelona, let’s talk about...

Yippee-Kai-Yay 2027 Summit in Denver

By

Next year the PASS Data Community Summit is in DENVER! and London, but Denver...

PASS Data Community Summit 2026

By

Yesterday was the first day of sessions at the PASS Data Community Summit (after...

Read the latest Blogs

Forums

Pay for Performance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Pay for Performance, which is...

Switching Schemas I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Switching Schemas I

Enforcing Unique Customer Emails When Duplicates Already Exist

By Imran2629

Comments posted to this topic are about the item Enforcing Unique Customer Emails When...

Visit the forum

Question of the Day

Switching Schemas I

I run this query:

SELECT 
 s.name AS schemaname
 , o.name AS objectname
 FROM sys.objects o
 INNER JOIN sys.schemas s ON s.schema_id = o.schema_id
 WHERE o.name = 'Beer'
I get one row back for an object named dbo.beer. There is an ETL schema and both of these are nonpartitioned tables. I run this code:
ALTER TABLE dbo.beer switch TO etl.beer
What happens?

See possible answers