Describes how SQL Server 2005 Data Mining allows aggregation directly at the algorithm level. Although this restricts what the third-party algorithm developer can support in terms of language and data types, it frees the developer from having to implement data handling, parsing, meta data management, session, and rowset production code on top of the core data mining algorithm implementation.
2009-04-22
1,606 reads
Given some input parameters, it generates the filegroups, files, partition function and partition scheme sql statements.
2010-05-28 (first published: 2009-04-17)
1,500 reads
2009-04-14 (first published: 2009-03-05)
2,095 reads
2009-02-12
3,101 reads
Building paging routines in SQL Server can be challenging since SQL wants to deal with full result sets. Adam Haines brings us a technique that you can use in SQL Server 2005 with the new Row_Number function.
2009-01-06
10,456 reads
2008-12-15
592 reads
This article is the beginner's guide to Default Trace. The article outlines how to query the default trace for key trace events, with a focus on DDL history.
2010-06-11 (first published: 2008-11-11)
54,385 reads
A quick way to get a snapshot of what data types are being used in all user tables.
2008-12-04 (first published: 2008-10-02)
1,140 reads
This script will reindex (online) any index eligible to be reindexed online. Accepts a day of week parameter for full offline reindexing.
2011-04-18 (first published: 2008-10-01)
4,714 reads
A short script you can incorporate into any 2005/2008 code to get the full schema.table.
2008-09-29
675 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 Risk Vs Reward, The never...
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...
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