Mining in-memory data
This article explains how desktop applications can use SQL Server 2005 Data Mining to analyze in-memory data.
2006-10-03
2,504 reads
This article explains how desktop applications can use SQL Server 2005 Data Mining to analyze in-memory data.
2006-10-03
2,504 reads
This article, published in the June 2005 issue of SIGMOD Record, provides an overview of SQL Server Data Mining from a standards perspective.
2006-05-24
2,097 reads
The two main functions of data mining are classification and prediction (or forecasting). Data mining helps you make sense of those countless gigabytes of raw data stored in databases by finding important patterns and rules present in the data or derived from it. Analysts then use this knowledge to make predictions and recommendations about new or future data. The main business applications of data mining are learning who your customers are and what they need, understanding where the sales are coming from and what factors affect them, fashioning marketing strategies, and predicting future business indicators.
2005-03-04
2,425 reads
An article from Microsoft Journal looking at the new Mining features of SQL Server 2005. If you're interested in Analysis Services, this ias a good look (from a high level) at the next version.
2004-08-19
1,617 reads
Provides audience with information on cluster analysis algorithm.
2001-05-07
1,594 reads
Running AI and data pipelines on the edge instead of the cloud has gone...
By Steve Jones
While writing another post I realized my UNION query didn’t work as one might...
By James Serra
Since the release of my book Deciphering Data Architectures: Choosing Between a Modern Data...
Comments posted to this topic are about the item Secure Cached Plans
Comments posted to this topic are about the item Complex Data Processing with dbt...
Comments posted to this topic are about the item Over or Under Provisioned
The DMV, sys.dm_exec_cached_plans, contains rows for each cached plan on an instance. In Azure SQL Database, not every used has rights to every database, as there does exist an instance behind each database. How is security handled for this DMV in Azure?
See possible answers