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.

(2)

You rated this post out of 5. Change rating

2012-03-19

135 reads

Blogs

Advice I Like: Failure

By

If it fails where you thought it would fail that is not a failure....

Logged in as a member of an Azure AD Group Error while Deploying DACPAC

By

Quite a long title for a short blog post ??While deploying a DACPAC (from...

Data Conferences – Worth Every Dollar

By

Some of the best career enhancers you can buy.   Why I Go to...

Read the latest Blogs

Forums

A Place where AI Technology Shines

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Place where AI Technology...

Alternate for xp_delete_file

By PJ_SQL

alternate for xp_delete_file

Select @ for different fields

By bswhipp

I have a need where I need to pass a field name to a...

Visit the forum

Question of the Day

Getting the Object Code

What happens when I run this on SQL Server 2022 in the AdventureWorks2022 database?

SELECT OBJECT_DEFINITION (OBJECT_ID(N'dbo.uspGetBillofMaterials')) AS [Object Definition]; 
GO 

See possible answers