Cannot create %S_MSG on view “%.*ls” because it uses the aggregate COUNT. Use COUNT_BIG instead.

Error Message:
Msg 10136, Level 16, State 1, Line 2
Cannot create %S_MSG on view “%.*ls” because it uses the aggregate COUNT. Use COUNT_BIG instead.

Severity level:
16.

Description:
This error message appears when you try to use the aggregate COUNT in an indexed view.

Consequences:
The T-SQL statement can be parsed, but causes the error at runtime.

Resolution:
Errors of the Severity Level 15 are generated by the user and can be fixed by the SQL Server user. The statement cannot be executed this way. You cannot use COUNT in a indexed view, you have to use COUNT_BIG instead.

Versions:
This error message was introduced with SQL Server 2000.

Example(s):
SET NUMERIC_ROUNDABORT OFF;
SET ANSI_PADDING,
    ANSI_WARNINGS,
    CONCAT_NULL_YIELDS_NULL,
    ARITHABORT,
    QUOTED_IDENTIFIER,
    ANSI_NULLS ON;
GO
IF OBJECT_ID (‘dbo.t’) IS NOT NULL
    DROP TABLE dbo.t;
GO
CREATE TABLE dbo.t
(
    c1 int NOT NULL PRIMARY KEY
);
GO
IF OBJECT_ID (‘dbo.V’, ‘View’) > 0
   DROP VIEW dbo.V;
GO
CREATE VIEW dbo.V
WITH SCHEMABINDING
AS
SELECT
    c1, COUNT(*) AS myCount
FROM
    dbo.t
GROUP BY
    c1;
GO

CREATE UNIQUE CLUSTERED INDEX cix_t_v
    ON dbo.V (c1);
GO

Remarks:
In the above example we try to create an index on view dbo.V. Because the view definition contains the aggregate COUNT, the error is raised.




Related Articles :

  • No Related Articles Found

No comments yet... Be the first to leave a reply!

Software Reviews | Book Reviews | FAQs | Tips | Articles | Performance Tuning | Audit | BI | Clustering | Developer | Reporting | DBA | ASP.NET Ado | Views tips | | Developer FAQs | Replication Tips | OS Tips | Misc Tips | Index Tuning Tips | Hints Tips | High Availability Tips | Hardware Tips | ETL Tips | Components Tips | Configuration Tips | App Dev Tips | OLAP Tips | Admin Tips | Software Reviews | Error | Clustering FAQs | Performance Tuning FAQs | DBA FAQs |