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/

DBCC CHECKDB is a repair command used by MS SQL Server users to detect and repair their corrupt databases. The command can be used with various parameters, such as, repair_rebuild and repair_allow_data_loss. Although the command proves helpful in resolving all kinds of logical corruption issues, there are certain problems that persists even after using the above command. Such situations occur when the database is badly corrupted. An easy way to access data in case of severe corruption is by restoring the database from an updated backup. However, in case of no backup available or backup falling short of restore the required database, you will need to use a powerful third-party MDF File Repair application.

Consider a real-time situation to describe the above problem. You attempt to mount your SQL database and see some consistency issues. To resolve these issues, when you run DBCC CHECKDB command, you encounter the below error message:

“Server: Msg 8929, Level 16, State 1, Line 1
Object ID 1979154096: Errors found in text ID 379493089280 owned by data record identified by RID = (1:647611:14) PK1 = 1300583.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 1979154096: Errors found in text ID 379544338432 owned by data record identified by RID = (1:648136:32) PK1 = 1300903.
…
Table error: Object ID 1979154096, index ID 255, page (1:558593). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 1979154096. The text, ntext, or image node at page (1:558593), slot 0, text ID 552407334912 is referenced by page (1:1387313), slot 46, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1 …
CHECKDB found 0 allocation errors and 33 consistency errors in table 'QTI_RESULT_DATA' (object ID 1979154096).
CHECKDB found 0 allocation errors and 33 consistency errors in database 'bb_bb60'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (bb_bb60 ).”

After the above error message gets displayed on the screen, the database records become inaccessible.

Cause:

The root cause for DBCC CHECKDB command to display the above error message is severe corruption of MS SQL database.

Resolution:

Below are some guidelines that help you to overcome the above error message:

Check if any system component is physically damaged. To do so, check the system, application, and SQL Server logs. Identify the component in the logs and swap it with a new component.
Run DBCC CHECKDB command with repair_allow_data_loss parameter. However, doing so might erase some of the critical data saved in your database. To avoid any situation, repair the database using an effective MDF Repair application. Such MDF Recovery tools can even be used by a non-database user.

SQL Recovery Software is a powerful and advanced repair tool that comprehensively repairs  MS SQL Server 2008, 20005, and 2000 databases. The MDF File Repair supports Windows 7, Vista, 2008, XP, 2003, and 2000.

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

I'm very happy to announce that the Postgres project has been selected to participate in this years Google Summer of Code program.

The PostgreSQL Project today released minor versions updating all active branches of the PostgreSQL object-relational database system, including versions 8.4.3, 8.3.10, 8.2.16, 8.1.20, 8.0.24, and 7.4.28.

The PostgreSQL Project today released minor versions updating all active branches of the PostgreSQL object-relational database system, including versions 8.4.2, 8.3.9, 8.2.15, 8.1.19, 8.0.23, and 7.4.27.

Mentat Technologies is happy to announce the new version of DreamCoder for PostgreSQL version 2.2, a powerful Windows solution for PostgreSQL administration and database development.

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

These new major features mean that we need you to participate in testing them.