Showing posts with label sql database. Show all posts
Showing posts with label sql database. Show all posts

Wednesday, 4 March 2015

SQL SERVER DATABASE FILE AND FILEGROUPS

SQL Server handles the bulky database of organizations. SQL supports two operating files one is data file and another is log files. There are three different formats for each file mdf and ndf file formats are for data files and all logs files are stored as .ldf format. The data file contains all the records, tables, indexes, views and stored procedure and all the transactions taken place in the database are being stored in log files. Later these log files can be used to recover all the transaction done in the database. As SQL Server is the best application but the default fact is that this is not immune to corruption. Mostly the issue involve in corruption is the repair of database so for this user mostly go for manual repair but there are certain issues involved with manual solution which may leads to failure of the manual solution in recovering database. So SQL Database Repair can be used in this case.

Types of database Files in SQL Server

SQL support three file formats for data and log storage. For the primary data .mdf files are used it store the master data and also known as master data files and for the secondary database .ndf files are defined. All the transaction information or can say log data are stored using .ldf format and referred as log files or transaction log files. Basically your secondary database files are optional one and the master database files are the permanent one. That means a database will surely have one .mdf file but the existence of .ndf is optional.

Types of Filegroups in SQL Server

SQL Server supports two filegroups. There is a primary filegroup which exist for every database and secondary filegroups are being created by the user. The primary filegroup contains all the primary files and system files are also allocated in the Primary filegroup. The user-defined filegroup contain secondary files created by the user.



Sunday, 1 March 2015

SQL SERVER ERROR 8930


“Table error: Object ID O_ID1, index ID I_ID1 cross-object chain linkage. Page P_ID1 points to P_ID2 in object ID O_ID2, index ID I_ID2.”

SQL database user many times encountered an above shown error message while using inbuilt utility DBCC CHECKDB database in ease to recover lost data. This error message displayed is known as error 8930 encountered in SQL database. SQL is referred as best database management and storage application used by the organizations. Occurrence of error 8930 is sign of corruption in database, so data recovery is important issue to tackle.



CAUSES OF ERROR 8930
The main cause of the occurrence of this error is the corruption of the database which doesn't allow the DBCC utility to recover data.
The incorrect page ID reference as shown in error message “P_IDI page refer to P_ID2” is the main cause of the error 8930. Page header corruption, hardware fault and virus attacks can be also are a main reason behind the occurrence of t his error 8930.

SOLUTION
If the error occurs the main concern is to recover data by resolving this error, mostly there are two ways to resolve the error. One is to go to manual solution and another way is to go for repair tool. Manual solutions to resolve this error is to perform hardware diagnose, back up restoration and to know more go to Error 8930 blog