Phil Factor

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

SQLServerCentral Editorial

Disconnected database development: solving a problem that needn't exist

A disconnected model is only really needed in the absence of a properly-defined database interface. We, as developers, create a rod for our own backs by insisting on treating a database in a way we wouldn't treat an object, let alone an assembly or namespace.

4.5 (2)

You rated this post out of 5. Change rating

2012-03-19

133 reads

Blogs

Modify Power BI page visibility and active status with Semantic Link Labs

By

Setting page visibility and the active page are often overlooked last steps when publishing...

T-SQL Tuesday #190–Mastering a New Technical Skill

By

It’s time for T-SQL Tuesday again and this time Todd Kleinhans has a great...

Getting Started with the MSSQL AI Agent in VS Code

By

Recently I was working in VS Code and I saw a walkthrough for the...

Read the latest Blogs

Forums

Password Guidance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Password Guidance

Using table variables in T-SQL

By Alessandro Mortola

Comments posted to this topic are about the item Using table variables in T-SQL

Azure elastic query credential question

By cphite

I am trying to check out elastic query between two test instances we have...

Visit the forum

Question of the Day

Using table variables in T-SQL

What happens if you run the following code in SQL Server 2022+?

declare @t1 table (id int);

insert into @t1 (id) values (NULL), (1), (2), (3);

select count(*)
from @t1
where @t1.id is distinct from NULL;
 

See possible answers