Change Tracking System in SQL Server 2012

Hi,
I have enabled change tracking to one of the database with retention period 1 day and auto clean is true. As per this setting changed data of one day old should get cleaned up automatically. But i am able to see 4 days
old data also using CHANGETABLE function. Let me know is there any other setting or is this an issue in SQL server 2012 which quires some patch?
SQL Server configuration: SQL Server 2012, Enterprise Edition, 64 bit.
Thanks in advance for the support.
Aruna Veluru

please paste out:
select * from sys.change_tracking_databases

Similar Messages

  • "block change tracking" equivalent in sql server

    Hi All,
    If someone has expertise in both oracle and sql server, pls let me know if there is " block change tracking" equivalent in sql server. I know sql server has incremental/differential backup, curious to know whether it got this equivalent feature.
    Regards,
    Satheesh Shanmugam
    http://borndba.com

    May be the below link will help you:
    http://www.databasejournal.com/features/mssql/article.php/3824196/Introducing-Change-Tracking-in-SQL-Server-2008.htm

  • How to export SSIS package to File system in SQL Server 2012

    I am accessing SSIS package by connecting to a database engine. I wanted to export the SSIS to file system. How to get it done in sql server 2012? I tried Util utility , i got package not present. Let me know what other options are available to export to
    file system?
    Mano

    Hi Mano,
    After exporting the project stored in a SSISDB catalog to an .ispac file, we can modify the extension .ispac to .zip, then, we can extract the zip file to get the .dtsx package files. Besides, please note that if there are project level connection managers
    or parameters, their definition cannot be exported to individual packages.
    Regards,
    Mike Yin
    TechNet Community Support

  • Linked Server unable to Connect in SQL Server 2012 after Restarting SQL Server Service it works fine. Why?

    I have created a Linked Server to Access Database of 64 MB in Size located in Remote System to SQL Server 2012.In Start for Some time it works fine and after it is giving the Error 
    OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.".
    Msg 7303, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
    Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
    Previously I thought it as Permission Issue. By trying some fixes proposed in forums it not fixed. But, after restarting the SQL Server Services without changes to the linked Server it works perfectly. How could i fix it. I don't want restart the SQL Server
    Service it leads to Some other process failures.
    RehaanKhan. M

    After all the Errors, When I am restarting the SQL Server its working correctly.
    Whats the problem it is clearing itself after restarting of SQL Server. Why ?. I can't find anything regarding this in SQL Server .
    The following are the Errors i got connecting to SQl Server.
    OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.".
    Msg 7303, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
    Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
    Error-2:
    Executed as user: RMS\Administrator. Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST". [SQLSTATE 42000] (Error 7303)  OLE DB provider
    "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" returned message "Cannot open a database created with a previous version of your application.". [SQLSTATE 01000] (Error 7412).  The step failed.
    After unchecking the Allow In Process in OLEDB.ACE Provider Properties.
    Msg 7399, Level 16, State 1, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
    The OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST" reported an error. Access denied.
    Msg 7301, Level 16, State 2, Procedure Insert_Records_Into_Actual_Calls_History, Line 29
    Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LANDLINE_TEST".
    for to fix above error i have followed the instructions in the following link,
    http://blogs.msdn.com/b/dataaccesstechnologies/archive/2010/08/19/permissions-needed-to-set-up-linked-server-with-out-of-process-provider.aspx
    This also failed to work. I Restarted SQL Server and make the Linked Server Properties Default to my Configuration and it works fine.
    Can you suggest me a solution for this issue. Every time i don't want to restart SQL Server Services as it effects other jobs and Processes.
    Thank you.
    RehaanKhan. M

  • Compatibility_level on SQL Server 2012 in-place upgrade

    Hi all,
    Based on BOL, master and user databases' compatibility_level will not be changed to 110 on SQL Server 2012 in-place upgrade.
    Database Compatibility Level After Upgrade
    The compatibility levels of the tempdb,
    model, msdb and
    Resource databases are set to 110 after upgrade. The
    master system database retains the compatibility level it had before upgrade.
    If the compatibility level of a user database was 90 or 100 before the upgrade, it remains the same after upgrade. If the compatibility level was 80 or less before upgrade, in the upgraded database, the compatibility level is set to 90, which is the
    lowest supported compatibility level in SQL Server 2012.
    I get the some result in our environment. So in-place upgrade SQL 2008 instance to SQL 2012 (both standalne and clustered), master/user databases' compatibility_level is 100. I also try to use SQL 2012 new function
    OFFSET and FETCH, it works.
    My concern is, whether we have to manually update the compatibility_level to 110? As SQL 2012 new features seem work even with compatibility_level <110, is there any problem if we leave it?
    (I didn't find any document about this, and related change metioned as a step for SQL 2012 in-place upgrade.)
    Any thoughts?
    MCSE:Data Platform

    So the idea is that if you have applications that are dependent on behaviour that changes, you can stay with the old compat level. I believe that there is some upgrade assistant to investigate whether this applies to you.
    On the top of my head, I don't recall any differences between compat levels 100 and 110, but there surely are some. But there are no new reserved keywords as I recall. And some things break even with the old compat level. (COMPUTE BY and the old RAISERROR
    syntax for instance.) So I don't think it is particularly brave to change the compatibility level. Change it back if something really breaks.
    The risk if you don't change it now, is that you have code developed on a dev server with compat level 110, which breaks when you deploy in production. And this happens one year from now, and no one recalls that this server has compat level 100, so it
    causes a lot of confusion and waste of time.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Geography fields in SQL Server 2012

    I have SQL Server 2012 running in 2012 mode.
    I run IIS 7.5 on Windows Server 2008.
    I use ASP.NET and after the login form, I issue a SQL select command which include the selection of a Geography field in the result.
    In order to make that work, I have to install:
    Microsoft SQL Server 2008 Shared Management Objects
    Microsoft SQL Server 2012 Shared Management Objects x86
    Microsoft SQL Server 2012 Shared Management Objects x64
    Microsoft System CLR Types for Microsoft SQL Server System 2008
    Microsoft System CLR Types for Microsoft SQL Server System 2012 x86
    Microsoft System CLR Types for Microsoft SQL Server System 2012 x64
    If I remove the 2008 installations, it will break. I do not understand why I have to continue to support old 2008 installation files just to benefit of Geography fields in 2012. It seems there is some kind of dependencies in 2012 in regard to Geography fields
    that it continues to require the installation of those 2008 components.
    I really need to get rid of that and only keep:
    Microsoft SQL Server 2012 Shared Management Objects x64
    Microsoft System CLR Types for Microsoft SQL Server System 2012 x64
    If someone has any idea, you may let me know.

    I have found a workaround for this issue.
    Type System Version=SQL Server 2012 can be added to the connection string. On all those alternatives I have found, this one is the simpler and does not require any change in the code.
    I was able to remove the following:
    Microsoft SQL Server 2008 Shared Management Objects
    Microsoft System CLR Types for Microsoft SQL Server System 2008
    ...and the application is now working.
    So, for now, I have those installed:
    Microsoft SQL Server 2012 Shared Management Objects x86
    Microsoft SQL Server 2012 Shared Management Objects x64
    Microsoft System CLR Types for Microsoft SQL Server System 2012 x86
    Microsoft System CLR Types for Microsoft SQL Server System 2012 x64
    I would like to keep only the 64-bit version but I need to keep the 32-bit version because I have some script that requires BatchParser. That one does not exist in the 64-bit version. So, once I installed back the 32-bit version, it went ok.
    The fact that I had to modify the connection string to have the Geography field to be workable in the ASP.NET application is an issue. I hope this will be resolved soon. I do not know if this has to be resolved at SQL Server level, .NET or ASP.NET.
    But, one thing for sure, I shouldn't have to plug that in the connection string to workaround such issue.

  • Change Tracking internals behave differently, SQL Server 2012 vs SQL Server 2008

    <original post by Glenn Estrada>
    Reposting an issue from Stack Overflow that a coworker and I are dealing with.
    In trouble shooting an issue with synchronizing disconnected devices with a central database server using Sync Framework 1.0, we are experiencing a problem after upgrading to SQL Server 2012 on the server. It appears that the CHANGE_TRACKING_MIN_VALID_VERSION
    is returning a value 1 higher than it should (or at least than it did prior to the upgrade.)
    I have been working thru Arshad
    Ali's great walk thru example of how to set up a simple example.
    I have run the scripts from #1 thru #5 to insert, delete, and update a row in the Employee table in both a SQL Server 2008 and a 2012 environment.
    In 2008, the following statement returns a 0:
    SELECT CHANGE_TRACKING_MIN_VALID_VERSION(OBJECT_ID('Employee'))
    In 2012, it returns a 1.
    In working thru a few more scripts (6-8) in the tests, I set the retention period to 1 minute to hopefully force a cleanup action. I left for the day and apparently it ran overnight.
    In the 2008 instance, the CHANGE_TRACKING_CURRENT_VERSION and the CHANGE_TRACKING_MIN_VALID_VERSION are equal (11). In the 2012 instance, the CHANGE_TRACKING_MIN_VALID_VERSION is one higher (12) than the CHANGE_TRACKING_CURRENT_VERSION (11). This could have
    an impact to the synchronization process when a database is idle for extended periods of time. And we have found that process could get caught in a loop, especially when the following test is performed to determine if a re-initialization, as opposed to synchronization,
    is required:
    IF CHANGE_TRACKING_MIN_VALID_VERSION(object_id(N'dbo.Employee')) > @sync_last_received_anchor
    RAISERROR (N'SQL Server Change Tracking has cleaned up tracking information for table ''%s''...
    Has anyone else experienced this change in behavior? Does anyone have an explanation?

    <original post by Glenn Estrada>
    Reposting an issue from Stack Overflow that a coworker and I are dealing with.
    In trouble shooting an issue with synchronizing disconnected devices with a central database server using Sync Framework 1.0, we are experiencing a problem after upgrading to SQL Server 2012 on the server. It appears that the CHANGE_TRACKING_MIN_VALID_VERSION
    is returning a value 1 higher than it should (or at least than it did prior to the upgrade.)
    I have been working thru Arshad Ali's
    great walk thru example of how to set up a simple example.
    I have run the scripts from #1 thru #5 to insert, delete, and update a row in the Employee table in both a SQL Server 2008 and a 2012 environment.
    In 2008, the following statement returns a 0:
    SELECT CHANGE_TRACKING_MIN_VALID_VERSION(OBJECT_ID('Employee'))
    In 2012, it returns a 1.
    In working thru a few more scripts (6-8) in the tests, I set the retention period to 1 minute to hopefully force a cleanup action. I left for the day and apparently it ran overnight.
    In the 2008 instance, the CHANGE_TRACKING_CURRENT_VERSION and the CHANGE_TRACKING_MIN_VALID_VERSION are equal (11). In the 2012 instance, the CHANGE_TRACKING_MIN_VALID_VERSION is one higher (12) than the CHANGE_TRACKING_CURRENT_VERSION (11). This could have
    an impact to the synchronization process when a database is idle for extended periods of time. And we have found that process could get caught in a loop, especially when the following test is performed to determine if a re-initialization, as opposed to synchronization,
    is required:
    IF CHANGE_TRACKING_MIN_VALID_VERSION(object_id(N'dbo.Employee')) > @sync_last_received_anchor
    RAISERROR (N'SQL Server Change Tracking has cleaned up tracking information for table ''%s''...
    Has anyone else experienced this change in behavior? Does anyone have an explanation?
    sql-server sql sql-server-2012

  • After sql server 2012 installation, I have changed sql server database engine service account from network service user to system user. What is disadvantages of this process?

         After
     sql server 2012 installation, I   attached my production db. Because of some reasons, i
     changed sql engine account from network service user to system user by means of sql server configuration manager.
         Now , there isn’t
     a problem at sql server running system.  But
    I have doubts that
     this can produce problems later. Because  sql server database engine account must have privileges that listed below;
    Log on as a service (SeServiceLogonRight)
    Replace a process-level token (SeAssignPrimaryTokenPrivilege)
    Bypass traverse checking (SeChangeNotifyPrivilege)
    Adjust memory quotas for a process
    (SeIncreaseQuotaPrivilege)
    Permission to start SQL Writer
    Permission to read the Event Log service
    Permission to read the Remote Procedure Call service
     While sql server installation, setup gives these
     privileges to network service user automatically, but changing user by means of sql confugarition manager does not give these
    privileges.
    Now, system user has privileges listed below. And sql server has been running for 1,5 months without any problems.
    Log on as a service (SeServiceLogonRight)
         Bypass traverse checking
    (SeChangeNotifyPrivilege) (Everyone user has his privileges. So i think that system user has this privilege also)
    What problems can occur because of this situation? Shall i give other privileges to system user and restart sql server or not? And how can i give these privileges to system user listed below;
    Replace a process-level token (
    this can be set from user rights assignments)
    Adjust memory quotas for a process
    (this can be set from user rights assignments)
    Permission to start SQL Writer ( 
    ? - give advice )
    Permission to read the Event Log service (
    ? - give advice )
    Permission to read the Remote Procedure Call service (
    ? - give advice )

     Our server is  windows server 2008 r2 enterprise edition. I have looked the bunch of permissions in user rights menu  that is in local security policy settings gui.
    And i have seen those permissions below were not granted to system user;
    Bypass traverse checking (SeChangeNotifyPrivilege)
    Adjust memory quotas for a process
    (SeIncreaseQuotaPrivilege)
    So, briefly you say, don't panic ?

  • Local Storage in SQL Server 2012 (Fast Track Appliance)

    Hello,
    Before procuring the Microsoft SQL Server 2012 Fast Track Appliance, we require additional information to satisfy the requirements from our infrastructure staff.  What type of data is stored in the local storage?  It seems that the local storage
    may be used for computations functionality only (temporary tables etc?); therefore, the only system backups that we may need to perform are for the main server and spare server which also contains all computation nodes (each SQL Server 2012 instance running
    on virtual machines?).  In fact, we probably don’t need any backups since the spare server provides a fail-over mechanism and allows for our engineers to “repair” any issues on the problem server? Also, If all of our data is already on a separate system
    outside of this data warehouse and can simply be exported back to the PDW system, then perhaps we don’t require backups? We simply use this data warehouse for analysis of the data (query and reporting).  The data collection and maintenance are permanently
    stored on a separate system.
    One last question, if required – could we remove the local storage and replace it with our enterprise SANs? – likely a performance hit; however, may still be better than having to integrate separate hardware components to try to replicate the fast track
    appliance and attempt to tune for performance.  Our infrastructure policy requires the use of enterprise SANs and reduction in local storage (possibly from new data center consolidation policies).
    Thank you for helping us to decide quickly and purchase this Fast Track Appliance expeditiously to meet our rapidly approaching deadline.  I have been unable to find answers to these questions from Microsoft pre-sales and tech support staff (without
    a support contract).
    Thank you,
    Vinh
    703-727-5377

    Hello,
    Thank you for the question.
    If the data in the local storage can be extracted from the PDW again, we don't need to backup them.
    As for the storage replacement, technically speaking, you can replace the local storage with the different SANs. However, if you do so, you will lead the system to a nonsupport scenario.
    Please refer http://msdn.microsoft.com/en-us/library/hh918452.aspx for further information.
    If you cannot determine your answer here or on your own, consider opening a support case with us. Visit this link to see the various support options that are available to better meet your needs:
     http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone
    Regards,

  • Creation of System Stored Procedure in SQL Server 2012 & SQL Server 2012 R2.

    Hi all,
    I am stuck at a point I am looking for a system stored procedure named 'sp_dboption' in SQL Server 2012  & R2 but could not find.
    Searched for it on the net and found that, this stored procedure 'sp_dboption' is now obsolete. So I tried to copy the content of 'sp_dboption' stored procedure from SQL Server 2008 R2 and create new system stored procedure with this name 'sp_dboption' in
    SQL Server 2012 but was unable to create the system stored procedure.
    Can you guys please tell me how to create system stored procedure in SQL Server 2012 & SQL Server 2012 R2. The reason of why I want to achieve this is because I have used 'sp_dboption' system stored procedure  in my application to create a database.
    As 'sp_dbotion' stored procedure is present in SQL Server 2008 R2 I am able to create the database in SQL server 2008 R2 but not in SQL server 2012.
    Can you please guide me how to create system stored procedure. I am out of luck.
    Please assist me, thanks & looking for help at the earliest. Hope someone will come to the fore and help me.

    Hi Vishwajeet,
    If you tried to create any object in the sys schema, you will get the error below.
    The specified schema name "sys" either does not exist or you do not have permission to use it.
    So I am afraid creating any object in sys schema is not supported by SQL Server. Here is a similar link for your reference.
    How to create table in SYS schema in SQL Server?
    Though sp_dboption is not in SQL Server 2012, does creating a user-defined one with the same content in 2008 make any difference in your business? You just need to specify the fully qualified name dbname.dbo.sp_dboption.
    If you are still interested in creating a system sp_dboption, you can register it with the
    sp_ms_marksystemobject.
    See
    Creating Your Own SQL Server System Stored Procedures.
    Eric Zhang
    TechNet Community Support

  • Errors while Changing the Database to Mutli User Mode from Single user mode in SQL Server 2012

    Hi,
    Good Afternoon :).  Need your help in resolving one of the issue with SQL Server 2012.
    Today, we kept one of the database in the Single User mode and wanted to bring back to Multi User mode.  But we are getting the below error.  There are no user sessions connected to this database which are blocking each other.  I see multiple
    SYSTEM sessions are in blocked state.  The blocking is not cleared even affter restarting the SQL services.
    Verified the SQL Server Errorlog and couldnt get much useful information to troubleshoot the issue.
    pasted the information from the sys.sysprocesses as well for your kind reference.
    Msg 1205, Level 13, State 68, Line 1
    Transaction (Process ID 55) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
    Msg 5069, Level 16, State 1, Line 1
    ALTER DATABASE statement failed.
    spid
    kpid
    blocked
    waittype
    waittime
    dbid
    login_time
    status
    cmd
    18
    1004
    36
    0x0005
    144
    5
    4/9/2014 13:13
    background                    
    TASK MANAGER    
    35
    1796
    36
    0x0005
    35
    5
    4/9/2014 13:34
    background                    
    TASK MANAGER    
    36
    2464
    37
    0x0005
    363
    5
    4/9/2014 13:34
    background                    
    TASK MANAGER    
    37
    5100
    36
    0x0005
    254
    5
    4/9/2014 13:04
    background                    
    TASK MANAGER    

    Clearly 36 and 37 are causing deadlock.
    see
    https://www.simple-talk.com/sql/database-administration/handling-deadlocks-in-sql-server/
    http://www.mssqltips.com/sqlservertip/1036/finding-and-troubleshooting-sql-server-deadlocks/
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • How to change backend databases sql server 2008 R2 to Sql server 2012 datacenter

    Hi
    i have current sharepoint 2010 form has backend database is sql server 2008 R2 on windows server 2008 R2 Enterprise
    and this form has
    1 application server
    1 Search server (index server)
    1 wfe server ( all web applications are running)
    1 databse server
    here  how i change this form back end to new windows server 2012 and sql server 2012 datacenter
    adil

    Information on SQL Aliases (using cliconfg.exe):
    http://sqlandme.com/2011/05/05/create-sql-server-alias-cliconfg-exe/
    You need to migrate content back into the database prior to migration:
    http://technet.microsoft.com/en-us/library/ff628255(v=office.14).aspx
    http://technet.microsoft.com/en-us/library/ff628257(v=office.14).aspx
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • [Forum FAQ] Reporting Service Point cannot be installed on a Site System Server running SQL Server 2012 SP1

    Symptom: When you install Reporting Service Point role on a Site System Server running SQL Server
    2012 SP1, you may encounter an issue that the Reporting Service Point role cannot be installed. The error log “srsrpMSI.log” and “srsrpsetup.log” may throw the error as shown in Figure 1 and Figure 2.
    03:32:03:764]:
    MainEngineThread is returning 1618
    Figure 1: Error -1
    <03/03/14 03:32:03>
    srsrp.msi exited with return code: 1618
    Figure 2: Error -2
    Reason: All the two logs indicate an error return code 1618. From the KB below you may know what
    the return code means.
    ERROR_INSTALL_ALREADY RUNNING 
    1618
    Another installation is already in progress. Complete that installation before proceeding with this install.
    KB link:
    http://support.microsoft.com/kb/290158 “it is related to an Office Suite KB, anyway, the MSI return code is the same meaning”
    You can look into Resource Manager and Event Viewer to find the other currently running MSI installation. You may get a warning in Event Log that means the MSI wants to install a SQL Server
    related Component (Figure 3). The Resource Manager confirms this (Figure 4).
    Event Log:
    Event ID: 1004
    Source: Msinstaller
    Level: Warning
    Detection of product '{A7037EB2-F953-4B12-B843-195F4D988DA1}',
    feature 'SQL_Tools_ANS', component '{0CECE655-2A0F-4593-AF4B-EFC31D622982}' failed.  The resource '' does not exist.
    Figure 3: Event Log
    Figure 4: Resource Manager
    Resolution: the error is exactly what the following KB describes.
    KB Link:
    http://support.microsoft.com/kb/2793634
    After we resolve the SQL Server 2012 issue, the Reporting Service Role is installed successfully.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    This implies that ODP.NET does NOT need to be installed on a client. However, I cannot find OraOPs9.dll on a machine with Client Release 9.2 installed. Should OraOps?.dll automatically come with a Client installation of 9.2 or higher?
    ODP.NET needs to be installed on the client. OraOps9.dll is part of ODP.NET, not the Oracle Client.
    Also, if an application is built with the 10g ODP.NET, can it be run from a machine with OraOps9.dll?
    If an application is built with 10g ODP.NET, it can be run with 9.2 ODP.NET as long as you do not use any 10g APIs. The new features in 10g ODP.NET are included in the doc and the ODP.NET FAQ for your reference.

  • SSRS 2012, SQL Server 2012. Problem with changing database

    Hi all!
    I have a problem with changing database for SSRS.
    I have a SSRS 2012 and SQL Server 2012. These programs is on WIndows Server 2012.
    I need to link SSRS to the new database instance. For this I run SSRS Configeration Manager, open tab Database, click Change Database. Then I choose option "Choose an existing report server database", click Next, write the server name, test
    connection (it's successed) and push Next again. Then I see this error message:
    Error
    The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services.
    OK   
    I'm confused, cause I have compatible versions of programs and THIS error.
    Please, help me.
    Thanks.

    Hi Kirill,
    From the error message, we can know that the issue may be caused by incorrect editions of SQL Server for report data sources are used as the Report Server Database.
    When creating a report server database, please be aware that not all editions of SQL Server can be used to host the database. So we should make sure that we have used the correct database as the
    Report Server Database. For more details, please refer to the “Report Server Database Server Edition Requirements” section in the following document:
    http://technet.microsoft.com/en-us/library/cc645993.aspx
    Hope this helps.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • SQL Server 2012 PowerPivot System Service not visible in Central Administration

    Hi all,
    I want to test PowerPivot 2012 on the following configuration:
    - Windows Server 2008 R2 
    - Sharepoint 2010 - Enterprise edition
    - SQL Server 2008 R2 
    - PowerPivot for Sharepoint<o:p></o:p>
    As such, I downloaded SQL Server 2012 Evaluation and tried to upgrade SQL Server 2008 PowerPivot for Sharepoint instance to SQL Server 2012 PowerPivot
    for Sharepoint. It didn't work as it's not possible to upgrade from Enterprise to Evaluation edition without a pid.
    Next, I uninstalled the existing SQL Server 2008 PowerPivot for Sharepoint and I installed the SQL Server 2012 PowerPivot for Sharepoint. 
    I started to configure PowerPivot in Central administration (http://msdn.microsoft.com/en-us/library/ee210609.aspx) , but I got stuck at the 2nd step Create and Configure a PowerPivot
    Service Application (http://msdn.microsoft.com/en-us/library/ee210685.aspx) in Central Administration.
    The problem is that both SQL Integration Service  and SQL Server PowerPivot System service are not visible in Central administration > Manage
    services on server; however they are visible and running in Windows Administrative Tools > Services.
    Do you think the services are missing in Sharepoint Central Administration because the Sharepoint configuration database is on SQL Server 2008, while the Powerpivot instance is on SQL Server 2012 ?

    Thank you for the suggestion.
    Meanwhile I have managed to solve the problem. What I've done:
    - remove PowerPivot configuration using the Power Configuration Tool
    - uninstall PowerPivot
    - reinstall PowerPivot
    - run PowerPivot Configuration Tool - I still got the parent service error
    - remove PowerPivot configuration using the Power Configuration Tool
    - run PowerPivot Configuration Tool - this time I received another error regarding the user that runs SQL Server Integration services
    - check  Sql Server Analysis Service account in Central Administration > Security > Service accountsManage service account - it seems that it was running under Local System account, although in Administrative Tools > Services it appeared to
    be run by my domain account
    - set a domain account for Sql Server Analysis Service in Central Administration
    - run the PowerPivot Configuration Tool - this time it went smoothly.
    The following url provides very useful info related to this type of issue: http://whitepages.unlimitedviz.com/2012/09/troubleshooting-and-removing-a-failed-installation-or-upgrade-of-powerpivot-for-sharepoint/

Maybe you are looking for