Set - 4

Question 6 :

In the SQL Server 2005 thesaurus XML configuration file, what is the expansion set?

Answer :

Expansion sets are synonyms for the search term and returned as results if they appear along with the search term.
The expansion set is the group of values that are synonyms and can be substituted for the search term. For example, an expansion set can be "SS2K5", "SQL Server 2005", "SQL2K5". In this case, fields with any of these 3 values would be returned as a result for searches on "SQL Server 2005".

Question 7 :

You are initiating a new replication subscription for one of the remote offices, but don't want to transfer it across the network. The snapshot files are 725MB, too large for your CD burner and there is no tape drive at the remote office. What feature of SQL Server 2005 would help you get the snapshot transferred?

Answer :

Compressed Snapshots
In SQL Server 2005, you can specify a snapshot to be compressed and it will be compressed using the CAB format. If it compresses enough, you should be able to burn it onto a CD.

Question 8 :

The TRUSTWORTHY database property is by default?

Answer :

The correct answer is off – The TRUSTWORTHY database property indicates whether the installed instance of SQL Server trusts the database such that it can reach out and perform actions outside the database. By default it is OFF such that the database to reduce certain threats that can result from attaching a database that contains potentially harmful code

Question 9 :

Where are Notification Services event messages logged in SQL Server 2005?

Answer :

In the Windows Application Log
Event messages are logged in the Windows Application log.

Question 10 :

What would happen when you execute the code below in Query Analyzer (SQL Server 2000)
USE Northwind
EXECUTE sp_who

Answer :

Information about current SQL Server users and processes is displayed.
The explanation could be found in the Books Online under Creating a Stored Procedure. One of the sections, named System Stored Procedures which describes how SQL Server looks up the system stored procedure has this note: Important If any user-created stored procedure has the same name as a system stored procedure, the user-created stored procedure will never be executed.