compatibility level of reportServer & reportserverTempdb changing to 100 every day at same time

  • Hi,

    We have performed the upgrade from SQL Server 2005 to SQL Server 2008 using Side-by-side upgrade method in a new server.

    After the upgrade, we have changed the compatibility level to 100 from 90.

    We also have installed SQL Server 2008 reporting services and reportServer & reportserverTempdb have configured and they are with compatibility level 100.

    But in the error log, I have noticed that the compatibility level of reportServer & reportserverTempdb changing to 100 every day at same time. I did nit understand why the error log says every day at same time the compatibility level has changing to 100 for freportServer & reportserverTempdb

    Is it normal behavior in SQL Server 2008?

    From the error log:

    010-08-17 05:24:12.57 spid61 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServerTempDB.

    2010-08-17 17:24:20.77 spid80 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServer.

    2010-08-17 17:24:20.97 spid80 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServerTempDB.

    2010-08-17 20:00:23.02 Backup Database backed up. Database: Mydb1, creation date(time): 2010/08/04(10:58:32), pages dumped: 78604, first LSN: 36763:3410:36, last LSN: 36763:3426:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\Mydb1_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:00:40.23 Backup Database backed up. Database: Mydb2, creation date(time): 2010/08/04(11:01:16), pages dumped: 44939, first LSN: 10755:7065:101, last LSN: 10755:7106:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\Mydb2_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:02:13.55 Backup Database backed up. Database: Mydb3, creation date(time): 2010/08/04(10:59:17), pages dumped: 405408, first LSN: 111666:3179:220, last LSN: 111666:3270:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\Mydb3_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:02:28.28 Backup Database backed up. Database: Mydb5, creation date(time): 2010/08/04(10:58:02), pages dumped: 2449, first LSN: 2756:1902:37, last LSN: 2756:1918:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\Mydb5_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:02:30.12 Backup Database backed up. Database: Mydb6, creation date(time): 2010/08/10(17:17:45), pages dumped: 6410, first LSN: 14789:3874:36, last LSN: 14789:3890:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\Mydb6_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:02:49.11 Backup Database backed up. Database: Mydb7, creation date(time): 2010/08/04(10:58:08), pages dumped: 70552, first LSN: 58219:23528:267, last LSN: 58219:23637:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\Mydb7_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:02:52.33 Backup Database backed up. Database: Master, creation date(time): 2010/08/04(13:39:20), pages dumped: 386, first LSN: 224:16:85, last LSN: 224:64:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\Master_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:02:53.22 Backup Database backed up. Database: Model, creation date(time): 2003/04/08(09:13:36), pages dumped: 170, first LSN: 21:456:37, last LSN: 21:480:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\Model_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:02:54.44 Backup Database backed up. Database: Msdb, creation date(time): 2008/07/09(16:46:27), pages dumped: 2060, first LSN: 2965:96:295, last LSN: 2965:224:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\Msdb_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:02:55.76 Backup Database backed up. Database: ReportServer, creation date(time): 2010/07/27(16:36:29), pages dumped: 458, first LSN: 50:41:37, last LSN: 50:57:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\ReportServer_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:02:56.60 Backup Database backed up. Database: ReportServerTempDB, creation date(time): 2010/07/27(16:36:31), pages dumped: 226, first LSN: 25:317:37, last LSN: 25:333:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\ReportServerTempDB_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-18 00:00:46.62 spid19s This instance of SQL Server has been using a process ID of 3808 since 8/4/2010 1:39:23 PM (local) 8/4/2010 8:39:23 PM (UTC). This is an informational message only; no user action is required.

    2010-08-18 05:24:27.94 spid64 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServer.

    2010-08-18 05:24:28.12 spid64 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServerTempDB

    Thanks

  • gmamata7 (8/18/2010)


    Hi,

    We have performed the upgrade from SQL Server 2005 to SQL Server 2008 using Side-by-side upgrade method in a new server.

    After the upgrade, we have changed the compatibility level to 100 from 90.

    We also have installed SQL Server 2008 reporting services and reportServer & reportserverTempdb have configured and they are with compatibility level 100.

    But in the error log, I have noticed that the compatibility level of reportServer & reportserverTempdb changing to 100 every day at same time. I did nit understand why the error log says every day at same time the compatibility level has changing to 100 for freportServer & reportserverTempdb

    Is it normal behavior in SQL Server 2008?

    From the error log:

    010-08-17 05:24:12.57 spid61 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServerTempDB.

    2010-08-17 17:24:20.77 spid80 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServer.

    2010-08-17 17:24:20.97 spid80 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServerTempDB.

    2010-08-17 20:00:23.02 Backup Database backed up. Database: Mydb1, creation date(time): 2010/08/04(10:58:32), pages dumped: 78604, first LSN: 36763:3410:36, last LSN: 36763:3426:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\Mydb1_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:00:40.23 Backup Database backed up. Database: Mydb2, creation date(time): 2010/08/04(11:01:16), pages dumped: 44939, first LSN: 10755:7065:101, last LSN: 10755:7106:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\Mydb2_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:02:13.55 Backup Database backed up. Database: Mydb3, creation date(time): 2010/08/04(10:59:17), pages dumped: 405408, first LSN: 111666:3179:220, last LSN: 111666:3270:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\Mydb3_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:02:28.28 Backup Database backed up. Database: Mydb5, creation date(time): 2010/08/04(10:58:02), pages dumped: 2449, first LSN: 2756:1902:37, last LSN: 2756:1918:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\Mydb5_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:02:30.12 Backup Database backed up. Database: Mydb6, creation date(time): 2010/08/10(17:17:45), pages dumped: 6410, first LSN: 14789:3874:36, last LSN: 14789:3890:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\Mydb6_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:02:49.11 Backup Database backed up. Database: Mydb7, creation date(time): 2010/08/04(10:58:08), pages dumped: 70552, first LSN: 58219:23528:267, last LSN: 58219:23637:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\Mydb7_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:02:52.33 Backup Database backed up. Database: Master, creation date(time): 2010/08/04(13:39:20), pages dumped: 386, first LSN: 224:16:85, last LSN: 224:64:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\Master_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:02:53.22 Backup Database backed up. Database: Model, creation date(time): 2003/04/08(09:13:36), pages dumped: 170, first LSN: 21:456:37, last LSN: 21:480:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\Model_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:02:54.44 Backup Database backed up. Database: Msdb, creation date(time): 2008/07/09(16:46:27), pages dumped: 2060, first LSN: 2965:96:295, last LSN: 2965:224:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\Msdb_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:02:55.76 Backup Database backed up. Database: ReportServer, creation date(time): 2010/07/27(16:36:29), pages dumped: 458, first LSN: 50:41:37, last LSN: 50:57:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\ReportServer_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-17 20:02:56.60 Backup Database backed up. Database: ReportServerTempDB, creation date(time): 2010/07/27(16:36:31), pages dumped: 226, first LSN: 25:317:37, last LSN: 25:333:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'Z:\Backups\ReportServerTempDB_08-17-2010.bak'}). This is an informational message only. No user action is required.

    2010-08-18 00:00:46.62 spid19s This instance of SQL Server has been using a process ID of 3808 since 8/4/2010 1:39:23 PM (local) 8/4/2010 8:39:23 PM (UTC). This is an informational message only; no user action is required.

    2010-08-18 05:24:27.94 spid64 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServer.

    2010-08-18 05:24:28.12 spid64 Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServerTempDB

    Thanks

    It's Reporting Services Service. It will not cause any harm.

    If you want to get rid of these messages you need to change reporting services startup service in windows services to "localsystem"

    Alex S
  • Out of curiosity, why would you want to run SSRS with a compatibility level of 90 as these databases are internal only.

  • Dave Klug (8/20/2010)


    Out of curiosity, why would you want to run SSRS with a compatibility level of 90 as these databases are internal only.

    OP wrote "After the upgrade, we have changed the compatibility level to 100 from 90"

    _______________________________________________________________________
    For better assistance in answering your questions, click here[/url]

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply