When discussing the normalisation process, it is always the First Normal Form that causes the most grief and confusion. Anith Sen takes up the challenge to explain, in simple terms, exactly what the First Normal Form really is, and why it is so important for Database Design. Along the way, he dispels some of the myths that have grown up around 1NF.
2009-06-09
5,827 reads
When moving data in related tables between databases, the order sometimes matters. New author Glen Cooper brings us an article that discusses the issues in maintaining referential integrity.
2009-03-20
6,286 reads
2009-03-13
2,159 reads
Adding a field to a database table is sometimes not as simple as it may seem. If certain situations are not considered when adding fields, you may find yourself looking at some long nights fixing database code. Today, database consultant Tim Chapman looks at two such scenarios, and how you can plan for their occurrence.
2009-03-04
4,537 reads
Maintaining a database often means schema changes. Before you change or delete anything, be sure to check for dependent objects.
2008-12-11
2,638 reads
In his first article for Simple-Talk, Joe Celko demystifies the use of Constraints, and points out that they are an intrinsic part of SQL and are a great way of ensuring that a business rule is done one way, one place, one time.
2008-10-30
2,846 reads
Inspired by what he recently found in some SQL Server shops, database architect Brian Walker shares advice for improved database design – and SQL Server performance.
2008-10-08
5,952 reads
Inspired by what he recently found in some SQL Server shops, database architect Brian Walker shares advice for improved database design – and SQL Server performance.
2008-09-26
5,999 reads
This paper presents an approach to the definition of function points within database-centric business information systems, the process of counting function points, .
2008-08-12
1,757 reads
Using the W3C OWL ontology standard lets you get more out of all kinds of data. Find out how this standard and some free software lets you query two databases as if they were one.
2008-08-06
2,110 reads
By Steve Jones
This value is something that I still hear today: our best work is done...
By gbargsley
Have you ever received the dreaded error from SQL Server that the TempDB log...
By Chris Yates
Artificial intelligence is no longer a distant concept. It is here, embedded in the...
Hi everyone I am writing an SP where there is logic inside the SP...
Comments posted to this topic are about the item Planning for tomorrow, today -...
We have a BI-application that connects to input tables on a SQL Server 2022...
I try to run this code on SQL Server 2022. All the objects exist in the database.
CREATE OR ALTER VIEW OrderShipping
AS
SELECT cl.CityNameID,
cl.CityName,
o.OrderID,
o.Customer,
o.OrderDate,
o.CustomerID,
o.cityId
FROM dbo.CityList AS cl
INNER JOIN dbo.[Order] AS o ON o.cityId = cl.CityNameID
GO
CREATE OR ALTER FUNCTION GetShipCityForOrder
(
@OrderID INT
)
RETURNS VARCHAR(50)
WITH SCHEMABINDING
AS
BEGIN
DECLARE @city VARCHAR(50);
SELECT @city = os.CityName
FROM dbo.OrderShipping AS os
WHERE os.OrderID = @OrderID;
RETURN @city;
END;
go
What is the result? See possible answers