If you run a trace (SQL Server Profiler), you can confirm the bug.
DECLARE @currVer nvarchar(128)
, @currMajorVer nvarchar(32)
, @idx int
, @currMajorVerInt tinyint;
SELECT @currVer = CONVERT(nvarchar(128), ServerProperty('ProductVersion'));
SET @idx = CHARINDEX('.', @currVer, 0);
SET @currMajorVer = SUBSTRING(@currVer, 1, @idx - 1);
SET @currMajorVerInt = CONVERT(tinyint, @currMajorVer);
DECLARE @dbname sysname
IF @currMajorVerInt = 10
BEGIN
SELECT @dbname = DB_NAME()
EXEC sp_dbcmptlevel
@dbname,
100;
END
USE [ReportServerTempDB]
IF @currMajorVerInt = 10
BEGIN
SELECT @dbname = DB_NAME()
EXEC sp_dbcmptlevel
@dbname,
100;
END
USE [ReportServer]
You can also confirm the 12-hour restart behaviour is as per default installation settings:
<Configuration>
<Service>
<RecycleTime>720</RecycleTime>
</Service>
</Configuration>
Specifies a recycle time for the application domain, measured in minutes. Valid values range from 0 to maximum integer. The default is 720.
http://msdn.microsoft.com/en-us/library/ms157273(v=SQL.100).aspx
No further action is required, unless you consider the merits of changing the RecycleTime.