Advanced

Technical Article

TACKLING DATA MODELERS' TOUGHEST CHALLENGE

  • Article

Recently, I began a Data Modeling “Master Class” by asking participants to nominate the toughest challenges facing them in their professional work. Virtually all the responses were about “soft” or “political” issues: persuading project teams to include a data modeling phase, negotiating territory with database technicians, gaining access to business people, and, of course, staying employed. No mention of normalization, star schemas, time-dependent data, exploiting new DBMS features, choice of language or indeed anything remotely technical

2005-05-20

2,661 reads

SQLServerCentral Article

Designing Cross Database Queries

  • Article

As systems get bigger, servers consolidated, and SQL Server back ends more types of applications, the need for cross database queries for reports, updates, and more will continue to grow. Steve Jones looks at a few ways that you can design your linkages and talks about why he prefers one over the other.

(45)

You rated this post out of 5. Change rating

2007-10-19 (first published: )

32,454 reads

SQLServerCentral Article

Data Archiving: Problems and Solutions

  • Article

SQL Server does an exceptional job at managing your data and making it available for your users and applications. However it doesn't know when you are done with data and there is not archival solution built. Author David Poole likens not having a strategy to leaving certain undesirable clothing items on your floor and provides some common problems and potential solutions based on his experiences.

(4)

You rated this post out of 5. Change rating

2005-02-16

13,799 reads

SQLServerCentral Article

Enforcing Referential integrity in Microsoft SQL Server 2000

  • Article

Referential Ingegrity is a critical part of any well designed RDBMS application, not just a part of Oracle, DB2, or some other platform. SQL Server has tools to make it easy, but a developer has to take the time to ensure that it is setup correctly, and ignorance is no excuse. New author Nick Duckstein brings us a look at basic RI and how you can set this up in your database.

(2)

You rated this post out of 5. Change rating

2005-01-17

14,242 reads

SQLServerCentral Article

Lookup Table Madness

  • Article

Are you mad? Not angry, more like crazy when it comes to designing databases in SQL Server? Don Peterson has met a few people he thinks are just that when it comes to building lookup tables. Does it stem from poor understanding of database design? Or do you disagree? Read Don's case against this particular design practice.

(27)

You rated this post out of 5. Change rating

2006-03-24 (first published: )

52,397 reads

SQLServerCentral Article

Codd's Rules

  • Article

Frank gives us his take on Codd's Rules. If you're new to databases, this is the core theory that resulted in the development of RDBMS. If you're more experienced with databases, maybe now is a good time to return to the rules to see how you're doing!

(1)

You rated this post out of 5. Change rating

2003-12-10

20,470 reads

Blogs

AI: Blog a Day – Day 4: Transformers – Encoder, Decoder, and Attention

By

Continuing from Day 3 where we covered LLM models open/closed and their parameters, Today...

Flyway Tips: Multiple Projects

By

One of the nice things about Flyway Desktop is that it helps you manage...

What DevOps Look Like in Microsoft Fabric

By

Microsoft Fabric (not to be confused with the more general term “fabric” in DevOps)...

Read the latest Blogs

Forums

Can an Azure App Service Managed Identity be used for SQL Login?

By jasona.work

I'm fairly certain I know the answer to this from digging into it yesterday,...

Azure Synapse database refresh

By Sreevathsa Mandli

Hi Team, I am trying to refresh the Azure Synapse Dedicated pool from production...

how to write this query?

By water490

hi everyone I am not sure how to write the query that will produce...

Visit the forum

Question of the Day

Fun with JSON I

I have some data in a table:

CREATE TABLE #test_data
(
    id INT PRIMARY KEY,
    name VARCHAR(100),
    birth_date DATE
);

-- Step 2: Insert rows  
INSERT INTO #test_data
VALUES
(1, 'Olivia', '2025-01-05'),
(2, 'Emma', '2025-03-02'),
(3, 'Liam', '2025-11-15'),
(4, 'Noah', '2025-12-22');
If I run this query, how many rows are returned?
SELECT *
FROM OPENJSON(
     (
         SELECT t.* FROM #test_data AS t FOR JSON PATH
     )
             ) t;

See possible answers