A Lookup Strategy Defined
Most databases designs nowadays seem to have at least a few if not many lookup or reference tables. This article helps you define a strategy in how to design, approve, and deploy them.
2003-02-20
13,327 reads
Most databases designs nowadays seem to have at least a few if not many lookup or reference tables. This article helps you define a strategy in how to design, approve, and deploy them.
2003-02-20
13,327 reads
Ever wanted to know how to reuse identity values after they're deleted? In this example by Dinesh, he shows you two methods to reuse the wholes in identity rows.
2003-02-18
8,773 reads
Steve Jones recently got bit by a bug the reminded him of the Y2K fiasco. Read about the problem and how Steve solved the problem.
2003-02-17
4,634 reads
These sets of scripts will add minimum password enforcement when a login is created or its password changes.
2003-02-14
172 reads
Jobs are pretty basic aren't they? They are until you get a couple hundred, or a thousand. Andy continues talking about managing jobs by standardizing how you handle notifications and failures, and talks about an interesting idea to monitor jobs separately from SQL Agent. Worth reading!
2003-02-14
8,468 reads
This article by new contributing member Bob Musser shows you how to reduce the amount of scans that SQL Server Agent does against databases. Not for the faint of heart.
2003-02-13
5,023 reads
An interview where they discuss their data strategy and integration with Visual Studio .Net
2003-02-12
3,288 reads
Although there are legitimate reasons for using filegroups, Chad Miller recently encountered a situation where they were used too much. He shows you in this article why and how to remove excessive filegroups.
2003-02-11
12,440 reads
In SQL Server 2000, there is a database option to close the database when it is not in use. Every wonder what this is? Or when it should be used? Steve Jones takes a look at this seldom used option.
2003-02-10
12,066 reads
There are times that you may find yourself on a project where you have one data source and need to publish to many subscribing databases. Often times, Replication is not looked at as a viable solution to achieving this goal. For this project, Demico and Lynn will demonstrate the way we utilized the Horizontal and Vertical partitioning capabilities that Microsoft has added to the Replication utility.
2003-02-07
5,491 reads
By Steve Jones
This is timely, as I’m currently on a boat in the Adriatic taking a...
You can find the slides and SQL scripts for my session “Spice up your...
By SQLPals
How to Clear the SSMS Cache (SSMS 21 and Later) Updated...
Comments posted to this topic are about the item Using CHOOSE()
Comments posted to this topic are about the item Re-Seeding a Broken Log Shipping...
Comments posted to this topic are about the item The DBA is Dead! Long...
We have this code that sets some status values and then queries them using the CHOOSE() function in SQL Server 2025.
CREATE TABLE Status
(
StatusID INT,
StatusDescription VARCHAR(20)
);
GO
INSERT dbo.Status
(
StatusID,
StatusDescription
)
VALUES
(0, 'Uncategorized'),
(1, 'Active'),
(2, 'Inactive'),
(3, 'Temp');
GO
SELECT CHOOSE(StatusID, 'Unknown', 'Active', 'Inactive', 'Temporary')
FROM Status;
When the SELECT runs, what is returned? See possible answers