SQL 2008 SP1 to SQL 2008 R2 Upgrade

I have a SQL server running SQL 2008 SP1 and am trying to upgrade to SQL 2008 R2.  The server has an installation of SCOM 2007 R2 with CU4 on it with reporting services and SCOM data warehouse
The SQL upgrade advisor runs and tells me that Custom report items were detected on the report server and 3x Custom extensions or assemblies were detected on the report server
If I actually try to run the upgrade I get a 2 failures in the Upgrade Rules check:
No Custom Security Extensions and No Custom Authentication Extensions
I can see that the file rsreportserver.config has the custom entries relating to the scom data warehouse user so it is possible to change this file back to the original config file that was present before installing scom data warehouse and then run the sql
upgrade and then put the config file back?

Hi Mickpell,
Me too facing the same issue while upgrading from SQL 2008 SP1 to SQL 2008 R2. Getting below error:
No Custom Security Extensions and No Custom Authentication Extensions
Did u follow the steps you mentioned and it is Success???. Could you please confirm. If it was success, I can proceed with the same steps. Thanks in advance!!! I am
using SCOM 2007 R2 CU5. Should I download latest Hotfix Utility or CU2 utility is enough???
Regards, Suresh

Similar Messages

  • Upgrading SQL 2008 R2 to SQL 2012 SP1

    Hi everyone,
    We are testing some upgrades in a lab environment. We have upgraded to SCCM 2012 R2 and are now looking at upgrading to SQL 2012 SP1 from SQL 2008 R2. Both SCCM and SQL are on one server. (The next step is to split SCCM and SQL but that's another topic)
    The question we are asking is, what should be our process for the upgrade? Do we need to stop SCCM services before doing the SQL upgrade? If, so, which ones?

    Hi,
    You need to stop all Configuration Manager services at the site.
    For the process of the upgrade, you could check the following document.
    http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigUpgradeDBSrv
    Best Regards,
    Joyce
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Upgrade FIM 2010 R2 Sp1 Databases from SQL 2008 R2 to SQL 2012

    Hi,
    I want to upgrade my SQL from 2008 R2 to SQL 2012.
    FIM Databases   
    1) FIMService Database 
    2) FIMSynchronizationService Database 
    Mentioned above are my FIM databases running on SQL server 2008 R2 . Now I was looking for some article which could tell me if SQL can be upgraded without affecting my existing databases of FIM or if i can move these databases to a new server having SQL
    2012
    Activity I want to perform :  Create a fresh  Server of SQL 2012 and move my FIM 2010 databases over it by restoring the backups. but as per the link below it seems not possible!
    http://social.technet.microsoft.com/wiki/contents/articles/5465.fimilm-how-to-move-the-backend-sql-server-synchronization-service-database.aspx

    Hi Shivam,
    Please take a look here: Release Notes for Forefront Identity Manager 2010 R2 SP1.
    In the table you have tasks to upgrade SQL for FIMService and FIMSych.
    FIM Service:
    Upgrade FIM Service servers to FIM 2010 R2 SP1
    Stop FIM Service on all servers
    Backup Database [in case rollback needed]
    Upgrade SQL to SQL Server 2012
    Start FIM Service on all servers
    FIM Synch:
    Upgrade FIM Sync to FIM 2010 R2 SP1
    Stop FIM Sync
    Backup Database [in case rollback needed]
    Upgrade SQL to SQL Server 2012
    Start FIM Sync
    If you are not making in-place upgrade, I would do something like here:
    Stop FIM Services
    Backup the databases at SQL 2008
    Restore backed up databases on SQL 2012
    Make sure SQL Agent Jobs are moved (FIMService)
    Make sure Broker is enabled on FIMService database
    On FIM machines create SQL alias using cliconfg utility. Alias should have the name of "old(sql2008) SQL" and point to new name/instance.
    Start FIM Services - they would use "old" name to connect, but it would be translated to new location. So they would start.
    If you found my post helpful, please give it a Helpful vote. If it answered your question, remember to mark it as an Answer.

  • Unable to upgrade SQL Server 2008 R2 to SQL Server 2012 SP1

    I'm encountering error after error, after successfully installing the upgrade advisor (which took some doing) and running it with essentially no warnings/errors (the one warning was on the connection strings, as I recall -- and all of the warnings had a
    "fix after" status.
    First failure involved SSRS and the inability to create the "managed account". Backed out the upgrade using http://sqldbanotes.blogspot.com/2013/10/how-to-fix-failed-in-place.html
    Now the failure involves SSAS and unable to connect to analysis services with name MSSQLServerOLAPService.  That is the logical name for the service, although it shows up as just MSSQLServer when looking at it in the services list.  I tried
    setting the service account to a local account as  well as to Local System -- did not make a difference, the upgrade couldn't apparently find it regardless.
    Has anybody successfully done an in place upgrade from SQL Server 2008 R2 to SQL Server 2012?

    Hi Bob，
    Thanks for your post and I am glad to hear that the issue is resolved. Thanks for you posting a reply to share your solution and I had marked it as answer. That way, other community members could benefit from your sharing.
    Regards,
    Sofiya Li
    If you have any feedback on our support, please click here.
    Sofiya Li
    TechNet Community Support

  • SCOM 2012 R2 database in-place upgrade SQL 2008 R2 to SQL 2012

    Hello,
    I intend to upgrade my SCOM SQL 2008 R2 environment to SQL 2012. I have (of course) an OPS, DWH and Reporting Services instances/databases.
    When I run the Update Advisor I run in to several issues.
    Has someone had experience with an in-place SQL update?
    Help would be appreciated.
    Greetings,
    Pim
    SCOM Administrator

    have a read at this detailed post by one of the MVPs
    http://thoughtsonopsmgr.blogspot.sg/2013/01/om12-sp1-upgrading-sql-server-2008-sp1.html
    Blog: http://theinfraguys.com
    Follow me at Facebook
    The Infra Guys Facebook Page
    Please remember to click Mark as Answer on the answer if it helps you in anyway

  • Moving Service Manager Database From SQL 2008 R2 SP2 to SQL 2012 SP1

    Hi Guys,
    Just looking for some clarification about moving our Service Manager 2012 R2 database to a new SQL Server.
    Our Service Manager database is currently on a remote SQL server, shared with other databases, running SQL 2008 R2 SP2. It was originally setup this way as we only deployed Change Management but we are now wanting to deploy everything, fully
    utilising SCSM/Orchestrator and Cireson's suite. Due to the limited resources available on that SQL server we are seeing performance issues before even getting it all up and running.
    I want to move the Service Manager database to a new dedicated SQL server running SQL 2012 SP1. I am aware of the official DB move procedure but it does not specifically mention moving up SQL versions. I have seen some comments around here that
    it is fine to do but some feedback would be good, it is not something I have done before. 
    All servers in this are fully patched Windows 2008 R2. Also, we do not currently have a Data Warehouse so do not need to worry about that. It was dropped and uninstalled before upgrading to Service Manager 2012 R2 and will be reinstalled after this DB move
    using a separate dedicated SQL server.
    Thanks, Chris.

    As long as your collations and permissions are the same as before it
    should not be a problem. That sad i could not find any other documentation saying it's not supported. 
    I have moved SCSM databases between different SQL-versions before and it has worked fine if the collations etc are correct. 
    Cheers,
    Thomas Strömberg
    System Center Specialist
    Blog:  
    Twitter:   LinkedIn:
    Please remember to 'Propose as answer' if you find a reply helpful

  • CRM 7.0 installation failed on Windows 2008 R2  SQL Server 2008 SP1

    Hello I'm currently trying to install CRM 7.0 on a windows 2008 R2 (64B) plateform  with SQL Server 2008 SP1 as database engine
    while launching sapinst.exe i'm facing this issue  that i cannot get rid of it 
    Could someone Help , would really be appreciated as i'm a newby on SAP world
    thanks a lot
    Unable to start a service execution.  Please check the following information for the possibble reason and inform the installation development :  Opened sylib701_1.dll exe dir is C:/Users/SAPINS1/AppData/Local/Temp/2/sapinst_exe.3492.1286357336 Opened C:/Users/SAPINS1/AppData/Local/Temp/2/sapinst_exe.3492.1286357336/iaguieng701_1.dll receiving and sending on port 21200 Environment variable SAPINST_JRE_HOME set to value 'C:/Users/SAPINS1/AppData/Local/Temp/2/sapinst_exe.3492.1286357336/jre'. exe dir is C:/Users/SAPINS1/AppData/Local/Temp/2/sapinst_exe.3492.1286357336 Creating file C:\Program Files\sapinst_instdir\x. Removing file C:\Program Files\sapinst_instdir\x. Opened C:/Users/SAPINS~1/AppData/Local/Temp/2/sapinst_exe.3492.1286357336/iakdblib701_1.dll  This is SAPinst, version 701_1, make variant 701_REL, build 1015514 compiled on Oct 3 2008, 01:51:15  MessageLib initialized successfully. showing dlg diProductChoice <dialog sid="diProductChoice"> <title>Welcome to SAP Installation Master</title> <dialog/> Login in progress Connection request to guiengine backend by host 169.254.138.68 Protocol version is 3.1 Send connect information client logged on Waiting for an answer from GUI CDialogHandler: ACTION_NEXT requested <dialog sid="diProductChoice"> <dialog/> Creating file C:\Windows\System32\x. Removing file C:\Windows\System32\x. showing dlg diRestartOrCancel <dialog sid="diRestartOrCancel"> Dialog does not contain standard input handler, so the backend is not able to generate a log entry <dialog/> Waiting for an answer from GUI current working directory is C:/Windows/System32 Creating file C:\Program Files\sapinst_instdir\x. Removing file C:\Program Files\sapinst_instdir\x. Unable to open URL file://C:\Windows\System32\control.xml.  The execution will be terminated now.

    Hi!
    Windows 2008 R2 is not yet listed in the PAM - and hence not yet supported. The technical prerequisites are met (with a special kernel patch) but not all software is released, so you may get it to run technically but not everything is tested and so, you should not install any SAP system on it!
    In fact, and just to provide you further details it is not possible to expect the 710 products released for Windows Server 2008 R2 before around four weeks; 700 products will be released even after 710.
    See [SAP note 1383873|https://service.sap.com/sap/support/notes/1383873]  ("Windows Server 2008 R2 Support").
    You can be always up to date with the latest Windows news at:
    [SAP on Microsoft Windows|SAP on Microsoft Windows] --> Support of Microsoft Windows Server 2008 R2
    Cheers!

  • Error while trying to upgrade SQL 2008 (SP2) to SQL 2012: There was a failure to calculate the applicability of setting LICENSEPATH.

    Hi,
    I am trying to upgrade one of our SQL Server Enterprise (2008 (SP2)) to 2012. I am using the upgrade option but it gives me the following error:
    Error Code 0x85640002: There was a failure to calculate the applicability of setting LICENSEPATH
    We have downloaded the image from our Volume Licensing account. Also, the same image was used to install SQL 2012 on Windows Server 2012 R2 servers without any issues.
    Below is the install summary.txt. I have tried everywhere but no go. Would really appreciate any assistance.
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2057043966
      Exit facility code:            1380
      Exit error code:               2
      Exit message:                  There was a failure to calculate the applicability of setting LICENSEPATH.
      Start time:                    2014-02-28 10:58:49
      End time:                      2014-02-28 10:58:58
      Requested action:              RunRules
      Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0x0BA02FC6%400x294A9FD9&EvtType=0x0BA02FC6%400x294A9FD9
    Machine Properties:
      Machine name:                  xxxxxxx
      Machine processor count:       2
      OS version:                    Windows Server 2008 R2
      OS service pack:               Service Pack 1
      OS region:                     U.A.E.
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Package properties:
      Description:                   Microsoft SQL Server 2012
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      SPLevel:                       0
      Installation location:         D:\x64\setup\
      Installation edition:          
    User Input Settings:
      ACTION:                        RunRules
      CONFIGURATIONFILE:             
      ENU:                           true
      FEATURES:                      
      HELP:                          false
      INDICATEPROGRESS:              false
      INSTANCENAME:                  <empty>
      PID:                           *****
      QUIET:                         true
      QUIETSIMPLE:                   false
      RULES:                         GlobalRules
      UIMODE:                        Normal
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140228_105848\ConfigurationFile.ini
    Rules with failures:
    Global rules:
    There are no scenario-specific rules.
    Rules report file:               The rule result report file is not available.
    Exception summary:
    The following is an exception stack listing the exceptions in outermost to innermost order
    Inner exceptions are being indented
    Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingApplicabilityException
        Message:
            There was a failure to calculate the applicability of setting LICENSEPATH.
        HResult : 0x85640002
            FacilityCode : 1380 (564)
            ErrorCode : 2 (0002)
        Data:
          SettingId = LICENSEPATH
          WatsonData = Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingApplicabilityException@2
          DisableWatson = true
        Stack:
            at Microsoft.SqlServer.Chainer.Infrastructure.Setting.CalculateApplicability()
            at Microsoft.SqlServer.Configuration.BootstrapExtension.ValidateChainerSettingAction.ExecuteAction(String actionId)
            at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
            at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
        Inner exception type: Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingValueException
            Message:
                    There was a failure to calculate the default value of setting LICENSEPATH.
            HResult : 0x85640001
                    FacilityCode : 1380 (564)
                    ErrorCode : 1 (0001)
            Data:
              SettingId = LICENSEPATH
              WatsonData = Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingValueException@1
            Stack:
                    at Microsoft.SqlServer.Chainer.Infrastructure.Setting`1.CalculateValue()
                    at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallQueuedSubscriberDelegates()
                    at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.Publish(Publisher publisher)
                    at Microsoft.SqlServer.Chainer.Infrastructure.Setting.CalculateApplicability()
            Inner exception type: System.ArgumentException
                Message:
                            Culture ID 3072 (0x0C00) is not a supported culture.
                            Parameter name: culture
                Stack:
                            at System.Globalization.CultureInfo..ctor(Int32 culture, Boolean useUserOverride)
                            at System.Globalization.CultureTable.GetCultures(CultureTypes types)
                            at Microsoft.SqlServer.Configuration.SetupExtension.LcidUtilities.GetLangPackParentFolderForLcid(String lcid)
                            at Microsoft.SqlServer.Configuration.SetupExtension.LcidUtilities.GetLcidFolder(ServiceContainer context, String baseFolderFullPath)
                            at Microsoft.SqlServer.Configuration.SetupExtension.LicensePathSetting.DefaultValue()
                            at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallFunctionWhileAutosubscribing[T](SubscriberDelegate
    subscriberDelegate, Int32 priority, AutosubscribingFunctionDelegate`1 function)
                            at Microsoft.SqlServer.Chainer.Infrastructure.Setting`1.CalculateValue()
    Regards,
    Mohammed

    Culture ID 3072 (0x0C00) is not a supported culture.
                            Parameter name: culture
    This appears to be the root problem. It seems that the regional settings on this machine is messed up. 0x0C00 is an unusual LCID, they do not normally not end in two zeroes.
    is there a custom culture installed on this machine?
    Review the regional settings and also check the System locale. If it looks spooky, set it to Arabic - U.A.E. if this is where you are located.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • SQL Express 2008 R2 and SQL 2005 Server SP1 in single Windows 2003 server

    Hi,
    I am using a Windows Server 2003 R2 Enterprise Ed SP2 OS with SQL 2005 SP1 intallled on it for our Nav 5 database.
    As my backup software requires SQL Express 2008 R2 as default daabase, is it possible to install this in the same server with the SQL 2005 currently running on it? Would there be any impact on the existing SQL 2005 and the application and the Navision database
    on it?
    Appreciate your help.
    Sharon Lo

    Hi,
    I am using a Windows Server 2003 R2 Enterprise Ed SP2 OS with SQL 2005 SP1 intallled on it for our Nav 5 database.
    As my backup software requires SQL Express 2008 R2 as default daabase, is it possible to install this in the same server with the SQL 2005 currently running on it? Would there be any impact on the existing SQL 2005 and the application and the Navision database
    on it?
    There is no issue with installing multiple versions of SQL Server on a machine.I have SS 2005 ,2008 R2 and 2012 all on same machine and they work just fine. You can install all version instances side by side and all will work independently from
    each other.
    Now issue which might cause problem  your SQL Server 2005 is SP1 which is a Blunder IMO. Please ASAP patch it to SP4 because you are running very old version of 2005 which is unsupported by Microsoft and also SP4 includes MANY fixes for SQLServer
    2005. Applying SP4 will fix many issues and will bring you under Microsoft support.
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
    My TechNet Wiki Articles

  • Upgrade MS SQL 2005 to MS SQL 2008 (R2) for High-Availability SAP ERP System

    Hi,
    We are having ECC 6.0 SR3 Hight-Availability system on windows cluster environment.
    Our platform is Windows Server 2008 SR2  with MS SQL Server 2005 SR3. We have two nodes in our windows cluster. Active-passive nodes.
    Node-1 is having CI, ASCS, ERS & DATABASE
    Node-2 is having DI, ERS & stand-by database software.
    I've check all the pre-requisites for sql upgrade.
    our kernel is on 700_Rel. I'm planning to stabilize the kernel with 721_Rel before Database upgrade.
    Support package patch level condition is met for sql upgrade in our scenario.
    Now we are planning to upgrade our MS SQL Server from 2005 sr3 to MS SQL Server 2008r2.
    Please provide me the steps for Kernel upgrade and sql upgrade to 2008r2 on Windows cluster environment.
    Thanks
    Venkat

    Hi Venkat
    1. Could you share your ECC support package level & also you can check the PAM
    2. Yes you can upgrade the MS Sql to 2008 R2, before starting upgrade Kindly ensure the full OS / DB level backup on both cluster node's
    3. MS Sql 2008 R2 upgrade refer the SAP Note
    1152240 - Setting Up Microsoft SQL Server 2008 (R2)
    4. For Kernel upgrade its release change kindly go thru the SAP Notes
    1713986 - Installation of kernel 721 (EXT)
    1728283 - SAP Kernel 721: General Information
    1726899 - 721 DCK: Upgrade from 7.0n to 7.1n
    BR
    SS

  • BPC 70 SP4 and SQL 2008 SP1 build 10.00.2531

    I am preparing a single server environment to host BPC 70 SP4.  The prerequisites indicate SQL 2008 with cumulative update pack 2 is supported (build 10.00.1779).  Will SQL 2008 SP1 (build 10.00.2531) work also?

    John,
    It will work but due to a critical issue of CU1. I recommend using CU2 or later.
    Thanks.
    James Lim.

  • Upgrade From SQL Server 2005 to SQL Server 2008 or 2012

    Hello this is a silly question but I was able to copy our old database to another hard drive and do an ATTACH to sql 2012 and it worked great now am I crazy or is this too good to be true

    Hello this is a silly question but I was able to copy our old database to another hard drive and do an ATTACH to sql 2012 and it worked great now am I crazy or is this too good to be true
    To be specific to your question.You can very well attach SQL 2005 database to SQL server 2008 and SQL server 2012.But how your application will respond to New database will be difficult to tell.
    I strongly recommend you to see below link
    Features depricated in SQL server 2012
    http://technet.microsoft.com/en-us/library/cc707782.aspx
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Migrating SQL 2008 DB to SQL 2012 for SharePoint Farm

    Our SharePoint 2013 Farm runs on ISCSI Disk on Windows 20008 R2 Standard SP1 Platform with SQL 2008 R2 Standard SP2.
    Now we are planning to move this ISCSI Disk to another SQL 2012 Standard Platform and then upgrade the SQL 2008 Databse to SQL 2012. Can some one please let me know what challenges we might face during this implementation.

    http://technet.microsoft.com/en-us/library/cc512723(v=office.14).aspx
    It depends if you want to move all, or just some, of your databases to the new server. If you need to move all of them that link describes the process but in short;
    Backup and restore all databases to the new server
    Configure the server roles and logins for the SharePoint accounts on SQL
    Create (or modify) your SQL alias to point to the new server

  • Difference between database features - SQL Server 2008 R2 navtive vs SQL Server 2012 with SQL Server 2008 compatibility set?

    I am investigating the impact of upgrading from SQL Server 2008 R2 to SQL Server 2012. To reduce the impact of the upgrade, I am planning to restore / create our application database onto SQL Server 2012 with compatibility level 100 (SQL Server 2008 and
    SQL Server 2008 R2).
    Are there any differences in feature support for database running in native mode on SQL Server 2008 R2 vs a database installed on SQL Server 2012 with compatibility level 100 set?

    Are there any differences in feature support for database running in native mode on SQL Server 2008 R2 vs a database installed on SQL Server 2012 with compatibility level 100 set?
    Yes there can be difference and impact there are few features deprecated in SQL Server 2012 you must be aware about that. Please see
    Deprecated Database Features in SQL Server 2012
    Deprecated SQL Server features in SQL Server 2012
    After you migrate database to 2012 please don't move ahead with production unless you have tested your application to new created database
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • SSIS Package developed in SQL Server 2008 R2 Using BIDS 2008 is not working in SQL Server 2012

    I am working in a Product based company.
    We have given a Pre-requisites to our customers like SQL Server version should be 2008 or later.
    I have developed and deployed my SSIS package in SQL Server 2008 R2 with BIDS 2008.
    I have used "Script Component" in my package.
    We will take only DTSX package file to the customer places and run using SQL Agent Job daily. 
    Who are all(Customer Environments) using SQL 2008 or R2 my package is running fine.
    Who are all(Customer Environments) using SQL 2012, I am facing the below issue 
    The component metadata for “Script Component, clsid {874F7595-FB5F-4OFF-9BAF-FBFF825OE3EF}” could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
    Still the same package is running fine for some of the customers having SQL 2012.
    I am getting the above error only for few customers.
    Can someone please guide me how to proceed on this. Is there any solution to go without upgrading the package to SQL 2012. Because we need to maintain only one package for all customers

    Hi Katherine,
    I am just using the script component only for generating Identity column purpose. I will get the maximum count from the table and using this count value as Input (JurisCount in my below code) for script component and increment the counter for new records.
    Finally I am mapping the Script component output value (JurisKey in my below code) to Key column of the table. That's all I am doing with Script Component.
    Here is my Simple .net code
    /* Microsoft SQL Server Integration Services Script Component
    *  Write scripts using Microsoft Visual C# 2008.
    *  ScriptMain is the entry point class of the script.*/
    using System;
    using System.Data;
    using Microsoft.SqlServer.Dts.Pipeline.Wrapper;
    using Microsoft.SqlServer.Dts.Runtime.Wrapper;
    [Microsoft.SqlServer.Dts.Pipeline.SSISScriptComponentEntryPointAttribute]
    public class ScriptMain : UserComponent
        public override void PreExecute()
            base.PreExecute();
              Add your code here for preprocessing or remove if not needed
        public override void PostExecute()
            base.PostExecute();
              Add your code here for postprocessing or remove if not needed
              You can set read/write variables here, for example:
              Variables.MyIntVar = 100
        int counter = 0;
        public override void Input0_ProcessInputRow(Input0Buffer Row)
            if (counter == 0)
                counter = Convert.ToInt32(Row.JurisCount);
            Row.JurisKey = counter;
            counter = counter + 1;
    PAVAN MSBI

Maybe you are looking for