HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Microsoft System Center Integration
- >
- Error during using DBCC CHECKDB
Microsoft System Center Integration
1828171
Members
2659
Online
109975
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2009 10:56 PM
06-07-2009 10:56 PM
Error during using DBCC CHECKDB
When I check my database integrity using DBCC CHECKDB with DATA_PURITY option enabled and it gives the below error message:
“Msg 2570, Level 16, State 2, Line 1
Page %S_PGID, slot %d in Object %d Index %d Column %.*ls value %.*ls is out of range for data type "%.*ls". Update column to a legal value.”
Please suggest me what to do to overcome this problem.
“Msg 2570, Level 16, State 2, Line 1
Page %S_PGID, slot %d in Object %d Index %d Column %.*ls value %.*ls is out of range for data type "%.*ls". Update column to a legal value.”
Please suggest me what to do to overcome this problem.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-08-2009 11:54 PM
06-08-2009 11:54 PM
Re: Error during using DBCC CHECKDB
To correct the above issue, you need to follow any of the below methods:
You should find the affected rows and manually update them with correct values. To do this, you can execute T-SQL (Transact-SQL) queries against the table or alternatively, refer to the information provided by error 2570. You can set it to any of acceptable default or specific value.
Note: You can not run DBCC command to repair the database as it can not determine the value to be placed instead of invalid column value.
In case if affected rows are large in number and it is not possible to update them manually, you can restore them from backup
If the above measure is not feasible because of backup unavailability or corruption, you need to use MDF Recovery applications to safely repair and restore your database. Such MDF Repair software use powerful scanning algorithms and offer advanced repair and restoration options together with interactive user interface. I like to suggest Stellar Phoenix SQL Recovery which is the foremost SQL Repair tool to repair damaged SQL databases.
http://www.mssqldatabaserecovery.com
You should find the affected rows and manually update them with correct values. To do this, you can execute T-SQL (Transact-SQL) queries against the table or alternatively, refer to the information provided by error 2570. You can set it to any of acceptable default or specific value.
Note: You can not run DBCC command to repair the database as it can not determine the value to be placed instead of invalid column value.
In case if affected rows are large in number and it is not possible to update them manually, you can restore them from backup
If the above measure is not feasible because of backup unavailability or corruption, you need to use MDF Recovery applications to safely repair and restore your database. Such MDF Repair software use powerful scanning algorithms and offer advanced repair and restoration options together with interactive user interface. I like to suggest Stellar Phoenix SQL Recovery which is the foremost SQL Repair tool to repair damaged SQL databases.
http://www.mssqldatabaserecovery.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2009 03:48 AM
07-07-2009 03:48 AM
Re: Error during using DBCC CHECKDB
Both of these accounts only made one post, and they were created one day apart.
I think this thread is spam. Beware of apps sold by spammers.
I think this thread is spam. Beware of apps sold by spammers.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP