Articles

External Article

SQL Server 2000: .NET and the Death and Re-Birth o

In this month's article I will cover an aspect of SQL Server that always generates a great deal of, well, shall we say "discussion"—triggers. Love them or hate them, SQL Server 2000 will change they way you think about triggers and will probably alter the way you design your applications. Specifically, this month I will dive into cascading referential integrity (RI) and the new INSTEAD OF and AFTER trigger concepts in SQL Server 2000.

2001-07-27

1,539 reads

SQLServerCentral Article

SQLServerCentral.com Wrox Book Giveaway

Our first contest will begin July 23rd! We’ll be giving away a free Wrox book titled: SQL Server 2000 Database Design
to the individual who refers the most users to SQLServerCentral.com throughout the duration of the contest. The contest will last from July 23rd until July 29th.
To insure that each referral counts, make sure that each person you refer has your SQLServerCentral.com registered email address. Good luck!

You rated this post out of 5. Change rating

2001-07-23

59 reads

Blogs

T-SQL Tuesday #193 – A Note to Your Past, and a Warning from Your Future

By

I haven’t posted in a while (well, not here at least since I’ve been...

Keeping MS Docs Up to Date

By

One of the things that I like about the SQL Server docs (MS Learn...

Patch Tuesday – Where to get more information

By

For a number of years I have subscribed to Randy Franklin Smith's Patch Tuesday...

Read the latest Blogs

Forums

is there a no code way to limit an ssis extract from excel to the 1st 21 rows?

By stan

is there a no code way to limit an ssis extract from excel to...

Pivot but preserve all rows on Aggregate column

By getsaby

Hello Need help in pivoting this data set, the Pivot takes MIN/MAX on a...

any reason to avoid asking ssis to extract files from ftp

By stan

hi we have to replace talend which generally was used to move files. talend's...

Visit the forum

Question of the Day

What is the PRODUCT

In SQL Server 2025, what does this return?

CREATE TABLE Numbers
( n INT)
GO
INSERT dbo.Numbers
(
n
)
VALUES
(1), (2), (3)
GO
SELECT PRODUCT(n)
FROM dbo.Numbers

See possible answers