Are pages allocated on extends, however this pages are not used yet by any kind of objects. It means, SQL Server has 8 pages by each extent. If an object reside in a page of a certain extend, this space is allocated and used, but the rest of the space of the extend is allocated but unused because there are not objects.
Space Unallocated:
Space (extends) that is not in use, it means extends that are not allocated by SQL Server. Any kind of grow will produce a space unallocated.
Exit message:MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = '{8BDD006D-7863-4D25-9806-08527E285EA4}'. Error code: 1605.
Start time:2009-07-28 18:30:43
End time:2009-07-28 18:31:14
Requested action:ComponentUpdate
Log with failure:C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20090728_182952\Detail_ComponentUpdate.txt
Exception help link:http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.1600.22%26EvtType%3d0x4E099C65%400x7B130144
The error happened during the installation of a SQL Server 2008.
Solution / Fix / Workaround
The above remark line show us the product code related with the error. First, is necessary to know that SQL Server 2008 has around of 30 products registered on the Registry. Each product has a Product code and an installation code as well (GUID).
For this case the Product Code is the following:
{8BDD006D-7863-4D25-9806-08527E285EA4}
The Installation Code is build with the product code in reverse form:
D600DD8368752D460894AE582E72580
One time that you got the Installation Code look into the Windows Registry and delete all the entries found.
Then try again the installation and the result must to be SUCCESSFULLY.
Sometimes is necessary take a full backup or log backup for a database without affect the backup normal sequence for the database and log as well. This backup can be with different purpose as testing, development, etc. For this cases SQL Server provides an option for the backup statement, this is COPY_ONLY.
This option is present when sp_configure is executed or when sys.configuration is queried, but this functionality is unavailable since SQL Server 2005, it is obsolete. Direct updates to system objects are not allowed. If sp_configure is used to enable the option, this configuration has not effect. In previous versions as SQL Server 2000 this functionality is available.
Testing the option
The following code enable the option “allow updates”, then a table is created and finally an update to system table is executed:
sp_configure'allow updates', 1
GO
RECONFIGUREwith override
GO
CREATETABLE TBLTEST (TESTFIELDINT)
GO
updatesys.objects
setname='TBLTEST_1'
wherename='TBLTEST'
GO
When the update to system table is triggered the following error is shown:
Msg 259, Level 16, State 1, Line 1
Ad hoc updates to system catalogs are not allowed.
SQL Server 2005 introduces Dynamic Management View, one of this objects allows us monitoring the progress for different tasks and process in SQL Server.
The Server configuration option called Agent XPs is used to enabled the SQL Server Agent extended stored procedures on the server. When this option is disabled, the SQL Server Agent node is not enabled in SQL Server Management Studio and you can not use the SQL Server Agent Service.
When the SQL Server agent is restarted, the extended stored procedures are enabled automatically.
The sys.configuration catalog view allow us to see the same values than sp_configure with “show advanced options” enabled. Even this Catalog view show us extra information because is possible to know if an option is or is not an advanced option, or if is or is not dynamic option.
Important Columns,
Value:Configured Value for the option
Minimum: Minimum Value for the option
Maximum: Maximum Value for the option
Value_in_use: current running value for the option.
Is_dynamic: it column allow us to know if the option is dynamic or not. 1 = the value takes effect when the RECONFIGURE statement is executed. 0 = the value takes effect when the SQL Server is restarted.
Is_advanced: it column allow us to know if the option is advanced. 1 = advanced option, it means that the option is displayed and can be changed just when “show advanced options” is set through sp_configure.
Now we are going to see statements using sys.configurations that are equivalent than sp_configure.
Using sp_configure is impossible to know if an option is dynamic.
Conclusion.
Using sys.configurations to see the server configuration is better than sp_configure because with a single select statement is possible to view all the server options with extra information as is_dynamic and is_advanced values, this extra information is impossible to obtain with sp_configure. Any changed necessary on the server configuration has to be performed with sp_configure.
Database specialist, currently I am working with differents databases as DB6, MAXDB, Oracle and SQL Server in SAP Environments.
My expertise area and strongest skills is working with SQL Server environments.