Search
Subscribe
Categories
- Backup and Restore
- Capacity Planning
- Compression
- Configure
- Contact me
- CPU
- Data Architecture
- Data Import and Export
- Database Mirroring
- DBA
- DBA Scripts
- DBCC
- Deadlocks
- Default Trace
- Development
- Disaster Recovery
- Disk Storage
- DMV
- Documentation
- Event Log
- Execution Plan
- Function
- High Availability
- Indexes
- Install & Setup
- Interviews
- IO Subsystem
- Isolation levels
- Jobs
- Latches
- Links
- Locking
- Memory
- Monitor Performance
- MS DTC
- MSDB
- Network
- Object Management
- Pagination
- Partitioning
- Performance
- Powershell
- Security Management
- SQL Agent
- SQL Azure
- SQL Blocking
- SQL Cachestore
- SQL DAC
- SQL Default Trace
- SQL DTS
- SQL Error Logs
- SQL Execution Plan
- SQL Optimizer
- SQL problems
- SQL Query Tuning
- SQL Server Error Tips
- SQL Server Management Studio
- SQL Server Profiler
- SQL Server Tuning
- SQL Trigger
- SQL View
- SQLServer-DBA News
- SSIS
- Statistics
- Stored Procedure
- T-SQL
- TempDB
- Tools
- TPC-H
- Transaction Logs
- View
- Virtualization
- Wait Stats
SQLServer-DBA.com Links
Recent Posts
- Forgotten sa password
- Sql server installation is either corrupt or has been tampered with error getting instance id from name
- Find Weak passwords in SQL Server
- Event ID 55 : The file system structure on the disk is corrupt and unusable on volume
- Career in DBA
- Error 3254 – The volume on device BACKUP_PATH is empty
- SQL auto close - Keep it turned off
- Windows Pagefile size for dedicated SQL Servers
- SQL Database Corruption
- max server memory and sql server memory – why is total memory greater than max memory?
16 June,2012 by Jack Vamvas
Question: During a regular maintenance UPDATE STATISTICS tasks I’m getting the following error:
Cannot create or update statistics on view "dbo.myView" because both FULLSCAN and NORECOMPUTE options are required. [SQLSTATE 42000]
How can I fix it?
Answer: The UPDATE STATISTICS is trying to update statistics on a VIEW. On a SQL VIEW a FULLSCAN is required.
On a SQL Server Instance this can cause a problem – particularly if you’re running a catch-all script. A FULLSCAN could cause servere delays on an UPDATE STATISTICS job – if every object required a FULLSCAN.
Some options are:
1) Create different scripts for VIEWS
2) Use sp_updatestats - which only only updates on objects which need the update
Author: Jack Vamvas (http://www.sqlserver-dba.com)
Verify your Comment
Previewing your Comment
This is only a preview. Your comment has not yet been posted.
As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.
Having trouble reading this image? View an alternate.
Posted by: |