2001-06-14
5,668 reads
2001-06-14
5,668 reads
2001-05-25
4,031 reads
By default, all NT administrators of the domain that your SQL Server is installed in, have SA rights in every database. This presents interesting challenge for DBAs, political and technical. Does your NT administrator group need SA rights to every database? The answer is no.
2001-05-25
4,095 reads
This article by Andy Warren provides an introduction to some of the fixed database roles and things to consider when using them.
2001-05-17
4,729 reads
Poorly managed SQL Server Security can not only leave your SQL Server vulnerable, but also leave your NT Server and network open to attacks.
2001-05-14
6,575 reads
This article by Andy Warren discusses both how to use the Public Role and how using Public may cause you more problems than it's worth. Great examples!
2001-05-10
18,661 reads
Using the sa account in development is just plain dumb. Here are some reasons why!
2001-05-08
6,863 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