Return to Question

My initial strategy was to create statistics on the column with the NOCOMPUTE and SAMPLE 0 ROWS options. I was under the impression that SQL Server would not automatically create statistics on a column that already has a statistics object, but this has happened on our dev and QA servers. I don't know why the statistics were created and I've been unable to trigger that myself by running queries.

I know about sp_autostats but I need something to prevent the creation of automatic statistics. sp_autostats only prevents the statistics from being auto-updated.

My initial strategy was to create statistics on the column with the NOCOMPUTE and SAMPLE 0 ROWS options. I was under the impression that SQL Server would not automatically create statistics on a column that already has a statistics object, but this has happened on our dev and QA servers.

New statistics were created for COL_GROUP. My NORECOMPUTE statistic was not updated. I don't know why the statistics were created and I've been unable to trigger that myself by running queries.

I know about sp_autostats but I need something to prevent the creation of automatic statistics. sp_autostats only prevents the statistics from being auto-updated.

I know about sp_autostats but I need something to prevent the creation of automatic statistics. sp_autostats only prevents the statistics from being auto-updated.

My initial strategy was to create statistics on the column with the NOCOMPUTE and SAMPLE 0 ROWS options. I was under the impression that SQL Server would not automatically create statistics on a column that already has a statistics object, but this has happened on our dev and QA servers. I don't know why the statistics were created and I've been unable to trigger that myself by running queries.

If you want to suggest alternatives to preventing statistics creation keep in mind that the table is used in a view referenced by thousands of different queries. I do not have control over the queries that are run.

My initial strategy was to create statistics on the column with the NOCOMPUTE and SAMPLE 0 ROWS options. I was under the impression that SQL Server would not automatically create statistics on a column that already has a statistics object, but this has happened on our dev and QA servers. I don't know why the statistics were created and I've been unable to trigger that myself by running queries.