Thử nào

Mentat Technologies announces the release of DreamCoder for PostgreSQL 2.4, a powerful Windows GUI solution for PostgreSQL administration and database development.

This new version includes more than 10 new features and improvements over the previous version.

An IAM (Index Allocation Map) page consists of eight page Ids, collectively called mixed page array, and holds the pages that are allocated to the index. The IAM pages are used to optimize the tables by allocating and deallocating storage space. Sometimes the IAM page is not able to perform as expected. Such corruption instances can occur because of various reasons such as hardware malfunctions, virus infections, power outages, abruptly exiting SQL Server, etc. To resolve such situations, you should use appropriate corrective measures. In case, you are not able to recover SQL database then you should use a third-party SQL database repair software to do so.
Consider a scenario wherein you encounter the following error message while working on an SQL Server 2000 database:
"Page P_ID in database ID DB_ID is allocated in the SGAM SGAM_P_ID and PFS PFS_P_ID, but was not allocated in any IAM. PFS flags 'PFS_FLAGS'."
Cause:
The root cause of this error is that a page that is not reflecting as an IAM page and also not seen in the mixed page array of IAM page. This is quite contradictory as this page has mixed page bit set in its PFS byte.

 For Details Info Visit: http://www.articleblast.com/Computers_and_Internet/General/Rectifying_Error_8906_and_repairing_corrupt_database_in_SQL_Server_2000/

The DBCC CHECKDB command in SQL Server databases is used to check and repair any inconsistency in the databases. There are many extensions for this command that you can apply in various kinds of situations. However, at times when you this command finds any error on the system tables then it ends abruptly. Such cases can arise due to corruption in the database tables. In such situations, you should employ certain in-built workarounds to get the database repaired. If you are not able to recover the database using these methods, then you should use a third-party SQL database recovery software to recover SQL database.

Consider a scenario wherein you encounter the following error message while working on an SQL Server 2008 database:

"System table pre-checks: Object ID O_ID. Page P_ID has unexpected page type PAGETYPE. Check statement terminated because of an irreparable error."

Cause:

This error occurs during the first phase of the DBCC CHECDB command on the database table. In this phase, a page is found having a different type than the DATA_PAGE type. In the first page, this command does basic checks on the data pages of the system tables.

 

For details about how to recovers this errors visit: http://www.programmersheaven.com/user/markwillium/blog/5477-How-to-resolve-Error-7984-to-repair-SQL-Server-2008-database/

Mentat Technologiesis happy to announce the new version of DreamCoder for Oracle version 5.1, a powerful oracle database tool for administration and development.
The new enhancements now available in DreamCoder for Oracle 5.1 help to make the Oracle development faster, easier and more efficient.

In Microsoft SQL Server, if any transaction violates the integrity constraints during execution, database inconsistency occurs. The transaction leaves your MS SQL Server database in illegal state and it gets aborted with an error. Database inconsistency leaves your MDF (Master Database File) in an unusable and inaccessible state, which can lead to serious data loss. In such cases, a valid and updated backup come for your rescue. You can easily restore all your valuable data from current backup and prevent needs of sql recovery using third-party applications.

Read more from here:  http://hubpages.com/hub/Minimum-Repair-Option-for-the-SQL-Server-Database-Inconsistency-Issues

Mentat Technologies is happy to announce the new version of DreamCoder for MySQL version 5.3, a powerful MySQL database tool for administration and development.

This new version includes more than 10 new features and improvements over the previous version.

Don't miss your opportunity to learn from the MySQL experts via our free webcasts in June. All sessions include live presentations and interactive Q&A.

MS SQL Server provides the DBCC statements that are used to check and fix the databases for physical and logical consistency. There are various types of DBCC statements that you can use for the any particular purpose. However, at times these commands are not able to perform. The reason behind is that these database may have corrupted because of various reasons such as virus infections, hardware issues, human errors, etc. In such cases, you should use a third-party SQL repair software to repair SQL database.

Consider a scenario wherein you are working on an SQL Server 2000 database. In this, you use the DBCC CHECKTABLE command on a particular table to make it more scalable and achieve parallelism. However, the command failed to execute. An error message is displayed, that is:

“CHECKTABLE terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.”

Cause:

The root cause of this error message is that the internal query that was used by DBCC failed to deliver the desired result. It may be possible that the tempdb database has gone out of space or there is an inconsistent system table.
Resolution:

To resolve this error message, you should perform the following methods, preferably in the given order:

Check for hardware issues: You should run hardware diagnostics and check whether the issue is raised because of any malfunctioning hardware component. You can also check the error logs, or swap the hardware components to zero in on the source of the issue. Also, you can also consider reformatting the disks and reinstalling the operating system.

Restore from backup: You should check if the backup is updated and clean. If yes, then you should restore the database from its backup.

Run DBCC CHECKDB: You should run DBCC CHECKDB first without a repair clause, and then with the repair clause after determining the extent of corruption.
The aforementioned methods will be able to resolve the error message and you can access the database properly. However, if it is not so then you should use a third-party SQL data recovery software to repair the corrupted database. Such read-only tools are able to repair SQL databases by using fast yet sophisticated scanning algorithms thereby ensuring safe recovery of the corrupted database.

Stellar Phoenix SQL Recovery is an MDF repair software that repairs SQL database from all instances of corruption. It supports SQL repair of the corrupt databases created in SQL Server 2000, 2005, and 2008. This MS SQL repair tool is capable of repairing various database objects such as stored procedures, queries, triggers, database constraints, user defined data types, etc. It is compatible with Windows 7, Vista, Server 2003, XP, and Server 2000.

Edward Screven, Oracle's Chief Corporate Architect, discussed the current and future state of MySQL in his keynote at the MySQL Conference & Expo.