11 Replies Latest reply on Feb 3, 2016 1:31 PM by David Coggeshall

    Database Upgrade for FootPrints

      Share This:

      Good Afternoon,

       

      Is there a knowledgebase article on what needs to be done on the FootPrints front end server side after migrating SQL database from 2008 to 2012 environment?

        • 1. Re: Database Upgrade for FootPrints
          Nicolas Roome

          There should be nothing required from a FP12 end

          • 2. Re: Database Upgrade for FootPrints

            I am not on FP 12 as of yet.  Currently i am on FP 11.6 i want to migrate from SQL 2008 environment to SQL 2012 or SQL 2014 always-On.  The server names will change but i am unsure what needs to be updated on the application server side to point it to the correct database server or what other steps are needed.

            • 3. Re: Database Upgrade for FootPrints
              Myrianthe Marton

              OSSS,

               

              In your case I would contact BMC support.  They can provide official documentation for the database migration documentation you are requiring.   I do not recommend using the current Migration Tool available in the V 11 product.

               

              Best,

               

              Myrianthe

               

              Myrianthe Marton
              RightStar Systems

              • 4. Re: Database Upgrade for FootPrints

                Thanks, i agree.  My issue is we are a government agency and the renewal process for support takes a considerable amount of time for the funds to be available.  Right now we have been waiting to two years for support.  and BMC is not willing to assist on good faith until the funds are released so we are maintaining the environment while we investigate other ticketing software.  Our goal is to move away from FootPrints as a result.

                 

                Btw: i found this document do yo think it would help?

                 

                http://support.numarasoftware.com/support/articles.asp?how=%20AND%20&mode=detail&kcriteria=5269&ID=5397

                • 5. Re: Database Upgrade for FootPrints
                  Nicolas Roome

                  You really cant blame BMC on this We have a lot of government clients at various levels and we've always been able to get our clients to renew ontime. We have one in which we have an agreement with, their process sees their renewal come in a month late every year.

                   

                  But 2 years... That's way beyond good faith Really what it is, the powers that be don't want to spend the money. Kind of a poor reason to want to move off a software because the vendor doesn't want to support you when you're 2 years beyond your expiry. I'm sure you'd find yourself in similar waters with another vendor.

                  • 6. Re: Database Upgrade for FootPrints

                    Although, i understand your point we were paying for two years but with the budget restrictions we are no longer able to pay for multiple years just renew annually. Renewing annually at the price of 200 thousand plus require signatures and justification from many different offices within New York City government.  Aside from that we cannot pay for support of the current year unless we pay for support of the previous two years, so the cost will continue to mount.  This is just one reason why we are moving to another product.  The others have to do with the software and the needs of our organization as we grow. 

                     

                    I also thought about the same thing if we were to move to another vendor that we would have the same issue but there is other ticketing software out there that rates high and are cheaper to pay for support as well as allow you to integrate SSCM for asset management instead of purchasing Asset Core and paying for that license as well. 

                    • 7. Re: Database Upgrade for FootPrints
                      Nicolas Roome

                      The back-support pay is up to 3 years as I recall, and I believe is pretty standard in the industry. Since your support payment.. really I should call it maintenance, since that's what it is... covers both support and new versions. So vendors would lose money if their customers only purchased support every other year or every couple of years just to get access to new versions.

                       

                      Hopefully you find what you're looking for. With FP12 you can integrate with SCCM - like most products would be able to do - to import data. But a true 2-way integration à la Service Core to Client Management, is more difficult to find.

                      • 8. Re: Database Upgrade for FootPrints

                        Thanks for your input.  Have a good day.

                        • 9. Re: Database Upgrade for FootPrints

                          Good Morning,

                           

                          I followed these steps and the migration was successful.

                           

                          1. Stop the FootPrints Schedule Service and FootPrints Watch Service services on the FootPrints server (under Start -> Administrative Tools -> Services).
                          2. In IIS, pause or stop the web site FootPrints uses.
                          3. The database must now be backed up and restored.

                            1. Open up Microsoft SQL Server Management Studio (from either the source or target SQL server).
                            2. Connect to the source SQL server where the Footprints database exists that is to be moved via backup/restore.
                            3. Expand "Server Name -> Databases -> Footprints"
                            4. Right click "Footprints".

                              1. Select "Tasks"
                              2. Now select "Backups"
                            5. Select FULL backup and choose a location to hold this backup.

                              1. The default name will be footprints.bak
                              2. For example:

                                C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\footprints.bak
                            6. Press the OK button to begin the backup.
                            7. Copy footprints.bak from the location it was backed up to on the source SQL server to a suitable location on the target SQL server.
                            8. Connect to the target SQL server using the existing Microsoft SQL Server Management Studio console.
                            9. Expand "Server Name -> Databases"
                            10. Right click Databases and select Restore Database.
                            11. In the Restore Database window, do the following:

                              1. Enter "Footprints" in the "To database" field
                              2. Click on the radio button for "From Device"
                              3. Click on the square button on the right.
                              4. Click the "Add" button and select the location/path to the footprints.bak file.
                              5. Click OK
                            12. Execute the restore by clicking OK.
                          4. After the restore completes, an "FP" SQL login and password will need to be created, and made the owner of the restored database.

                            1. Select "New Query" on the left side of the top toolbar. This will open up a notepad-like interface tab in the Management Studio.
                            2. In this area, type in the following:

                              use Footprints
                              EXEC sp_addlogin 'FP', 'FP01012006u', 'Footprints'
                              EXEC sp_changedbowner FP


                              NOTE: If it is known the password for the SQL login which Footprints uses (the "FP" SQL login by default) has been changed from the default password of ('FP01012006u') to something else, substitute FP01012006u in the "EXEC sp_addlogin..." command above with the actual password use for the "FP" login.

                            3. Select the red exclamation mark/Execute button from the upper toolbar.
                          5. Now, the FootPrints application must be made aware of this change in database location.

                            1. The System ODBC DSN on the FootPrints application server must be re-configured to connect to the new SQL server where the FootPrints database was restored to.

                              1. On the FootPrints server, Select "Start -> Administrative Tools -> Data Sources (ODBC)"
                              2. In the "ODBC Data Source Administrator" window, select the "System DSN" tab.
                              3. Select the "Footprints" Data Source and press the "Configure..." button.
                              4. In the "Which SQL Server do you want to connect to?" field, provide the name of the newtarget SQL server and press "Next >".
                              5. Ensure "With SQL Server authentication using a login ID and password entered by the user" is selected, and the checkbox for "Connect to SQL Server to obtain default settings for the additional configuration options" is selected.
                              6. Type "FP" in the "Login ID:" field.
                              7. Provide the password for the "FP" account ("FP01012006u" or other password by default as specified in step "4.b." above for the "EXEC sp_addlogin..." command.
                              8. press "Next >".
                              9. If necessary, check the box labeled "Change the default database to:" and select the "Footprints" database.
                              10. press "Next >".
                              11. press "Finish >".

                                A new window should appear providing the details of the connection.
                              12. Press "Test Data Source". A message with the following text should appear:

                                Microsoft SQL Server ODBC Driver Version 03.86.3959

                                Running connectivity tests...

                                Attempting connection
                                Connection established
                                Verifying option settings
                                Disconnecting from server

                                TESTS COMPLETED SUCCESSFULLY!
                              13. Press the OK button.
                              14. Press the OK button on the window that provides details of the connection and contains the "Test Data Source" button.
                              15. Press the "OK" button on the main "ODBC Data Source Administrator" window.

                                If any errors are encountered in reconfiguring the ODBC Data Source to connect to the newtarget SQL server and the restored database, re-check the steps above to ensure they were performed correctly.
                            2. IF a password other than "FP01012006u" was used for the "FP" SQL login for steps "4.b." (creating the "FP" login in the new target SQL server) and "5.a.vii" (providing the password during the re-configuration of the System ODBC DSN), the C:\Footprints\cgi\MRlocalDefs file on the FootPrints application server will need to be edited to reflect this password.

                              1. On the FootPrints application server, make a backup copy of the C:\Footprints\cgi\MRlocalDefs file.
                              2. Open the MRlocalDefs file for editing in a text editor such as notepad, WordPad or another suitable text editor.
                              3. Locate the following line (should be found within the top 10-15 lines of the file):

                                $ALTERNATE_ODBC_PW = "FP01012006u";

                              4. Replace the password (in between the doublequote characters) with the actual password used in place of the default "FP01012006u" password. Ensure the doublequote characters remain before and after the password and the semi colon character (;) ends the line.
                              5. Save the MRlocalDefs file when done editing.
                          6. Once the previous steps are successfully completed, start the FootPrints Schedule Service and FootPrints Watch Service services on the FootPrints server (under Start -> Administrative Tools -> Services).

                          7. In IIS, restart the web site FootPrints uses.

                          8. Assuming all previous steps were successfully completed, it should now be possible to login to FootPrints and view/create/update issues and other data.
                          • 11. Re: Database Upgrade for FootPrints

                            IF anyone is looking for something similar for Version 12. This article seems to do the trick.

                             

                            http://support.numarasoftware.com/support/articles.asp?how=%20AND%20&mode=detail&kcriteria=7176&ID=7322