Set - 6

Question 21 :

You are setting up the backup scheme for your SQL Server 2005 server and want to setup nightly full backups and hourly log backups in the Maintenance Plans subsystem. How many plans must you setup?

Answer :

Since you have two separate schedules for the maintenance operations, you will need to have two separate plans to handle this need. Each plan can only be executed on one schedule, so one is needed for a single daily execution, the nightly full backups, and another for the hourly log backups.

Question 22 :

You have installed one new assembly on your SQL Server 2005 server and are wondering if it is being used on the production server. How can you easily monitor to see if this assembly is being used?

Answer :

You can monitor the Assembly Load event in a trace.
While you could scan trace results for the names of functions and procedures using the assembly, it is possible that you may not know all the places the assembly is being called from. There is a CLR Load event class that will capture an event when a CLR class is executed.

Question 23 :

You wish to ensure you can recover your SQL Server 2005 database to a point in time if necessary. Which recovery models can you use?

Answer :

Only the Full recovery model supports point in time restoration of your database.

Question 24 :

Does a root element in an XML document necessarily contain all the content for a well-formed document?

Answer :

By definition, the root element is required in a well-formed XML document and it contains all other content nested inside it.

Question 25 :

Which of the following datatypes can be represented in a SQL_VARIANT datatype?

Answer :

None of the above.
The SQL Variant type can store all datatypes except varchar(max), varbinary(max), xml, text, ntext, rowversion/timestamp (thought the data of a rowversion can be stored in a binary(8), which can be stored in a sql_variant) and sql_variant (it may seem strange that you can't store a variant in a variant, but all this is saying is that the sql_variant data type doesn't actually exist as such—SQL Server chooses the best type of storage to store the value you give to it).