locked
After database move to new server DB, historical data from before data "migration" not being displayed RRS feed

  • Question

  • Modified 3-server topology (VMWare, Windows Server 2008 SP2, SQL Server 2005 Standard): Mgmt/Coll/Rpt server; Coll/Rpt DB server; existing WSUS server

    Original FCS deployment (deployed June 2010) had DB server (unknowingly) running trial SQL Server 2005 Enterprise with license expiring. Created new DB server (same specs as original, but with licensed SQL Server 2005 Standard) and, on 11/26/10, after re-installing FCS components on Mgmt and new DB server, "migrated" data between the two DB servers by detaching/attaching OnePoint, SystemCenterReporting, and ReportServer DBs. Although the system seems to be working normally, historical data from before the "migration" seems to have gone missing (or cannot be accessed). How can this data be restored to the new system?

    Reporting Services Configuration seemed to have proceeded normally and successfully on Mgmt server. Also, on new DB server, initial DB sizing for SystemCenterReporting was set for 180 days retention (original DB server was set for default 395 days).

    FCS Management Console

    Works: # managed computers; 3 main computer status graphs; Computers Per Issue has numbers; able to view Summary reports; Policy Management shows correct policies; able to scan computers

    Issues: 14-day history shows no data, Summary reports show no historical data

    MOM

    Works: event collection; current Alerts data; computer tasks

    Issues: Unable to view individual computer event history past 11/26/10

    Admin Console

    Works: Computers lists current: All Computers, Unmanaged Computers, Agentless Managed Computers, Agent-managed Computers, Pending Actions

    Issues: Management Servers and Computer Discovery Rules are empty

    Monday, November 29, 2010 10:47 PM

Answers

  • Hi Russell,

    Thanks for the update.

    We may manually modify the tables of SQL Database to recover it. As I am not quite familiar with SQL Modification, you may re-post a new thread to our SQL Server TechNet forum for further assistance.

    http://social.technet.microsoft.com/Forums/en-US/category/sqlserver/

    Hope this helps.

    Miles 


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Miles Zhang Thursday, December 23, 2010 2:12 AM
    Wednesday, December 1, 2010 2:08 AM

All replies

  • Hi,

    Thanks for the post.

    First, we don't recommend migrating SQL Server 2k5 Enterprise to SQL Server 2k5 Standard in FCS environment as it may cause some data loss issue.

    In this case, I am wondering if you are using 'Scale-out deployment' on the original server. As we know, SQL Server Reporting Services scale-out deployment refers to an installation configuration that has multiple report server instances sharing a single report server database. This deployment model is used when you want to run
    Reporting Services in a server cluster. The Reporting Services edition must be Enterprise, Developer, or Evaluation. Standard edition does not support a scale-out
    deployment.

    Because you restored the databases and keys from the original server which has already had a record for the old reporting service. When you try to use a new report service to connect to the old database, SQL Server recognizes it as request in "Scale-out deployment", and the error can be trigger because the current SQL Server Edition (Standard) is not valid.

    Hope this helps.

    Miles

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, November 30, 2010 9:43 AM
  • Miles,

    Thank you for your reply.  I think you are correct about the scale-out deployment.  The new DB server event log show this recurring error:  "Report Server Windows Service has not been granted access to the catalog content."

    So basically, for this situation, it is not possible to retain the 5+ months of SQL Server 2K5 Enterprise data within our new DB server installed with SQL Server 2K5 Standard.

    --Russell

    Tuesday, November 30, 2010 7:36 PM
  • So this issue affects my current system's ability to store events on the database server?  No historical data is showing up on the dashboard or reports, even when I run the manual DTS process on the new DB server.

    Tuesday, November 30, 2010 11:05 PM
  • Hi Russell,

    Thanks for the update.

    We may manually modify the tables of SQL Database to recover it. As I am not quite familiar with SQL Modification, you may re-post a new thread to our SQL Server TechNet forum for further assistance.

    http://social.technet.microsoft.com/Forums/en-US/category/sqlserver/

    Hope this helps.

    Miles 


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Miles Zhang Thursday, December 23, 2010 2:12 AM
    Wednesday, December 1, 2010 2:08 AM