Page fault is referred to the situation when the process addresses a page in the working set of the process but the process fails to locate the page in the working set. And on a page fault the kernel updates the working set by reading the page from the secondary device.

Yes I have certainly worked on ADO.Net. ADO.net encompasses two groups of classes: content components and managed provider components. The content components include DataSet class and other supporting classes as DataTable, DataRow, DataColumn and DataRelation. The DataSet class is a lightweight cache of a particular database from the data store.  It allows reading and writing of data and schema in XML. ADO.Net involves disconnected datasets because it is geared towards a distributed architecture. All tables and relations in a DataSet are exposed through the DataSet tables and Relations properties.  E.g. Using System; Using System.Data;  DataSet ds = new DataSet("MyDS"); Ds.Tables.Add ("Order"); Ds.Tables["Order"].Columns.Add("OrderNo" Type.GetType("System.Int32"));  The DataSet tightly integrates with XML using the methods WriteXml, ReadXml, WriteXmlSchema and ReadXmlSchema

Check out MOLAP, ROLAP and HOLAP in SQL Server books online for more infomation.What are the new features introduced in SQL Server 2000 (or the latest release of SQL Server at the time of your interview)? What changed between the previous version of SQL Server and the current version?This question is generally asked to see how current is your knowledge. Generally there is a section in the beginning of the books online titled "What's New", which has all such information. Of course, reading just that is not enough, you should have tried those things to better answer the questions. Also check out the section titled "Backward Compatibility" in books online which talks about the changes that have taken place in the new version.

We use Bugzilla which is an opensource software for logging bug. While logging a bug we need to give detailed information about the whole steps i've done when i encountered this bug or defect. When we hit a defect i mean while executing some testcase if we encounter a bug , we need to inform the developers & also concerned like Program manager,Development Lead,Test Lead etc. Bug reporting is a process of such communication. The main aim of a bug report is to let the developers know the details of the failure & to help them to find a resolution for the issue . So it is very important to give detailed information so that whoever is reading the bug report or trying to reproduce the bug can do so easily . The bug report is a document that explains the gap between the expected result and the actual result and detailing on how to reproduce the scenario.

Write the bug report just when you are sure that you have found a bug, not after the end of test or at the end of the day. It might be possible that you might miss out on many crucial points if you are delaying the write up for bug filing . Worse, you might miss the bug itself. Put necessary time to diagnose the defect you are reporting. Think of the possible causes. You might land up uncovering more defects if there are any . Mention your discoveries in your bug report. The programmers will only be happy seeing that you have made their job easier. Take some time off before reading your bug report. You might feel like re-writing it.

If the speaker is defective, the resistance reading should be 0 for shorts or infinite for opens.