Database Upgrades

KB Home   |   Database Upgrades

Main.DatabaseUpgrades History

Hide minor edits - Show changes to output

Changed lines 34-35 from:
Summary:
to:
!!!Summary:
Added line 39:
----
Added lines 41-42:
----
[-keywords: database down time, upgrade plan, offline during upgrade-]
Changed lines 36-38 from:
--> [@Every 500,000 database rows@] = [@10 minutes@]

to:
-->[+ [@Every 500,000 database rows@] '''=''' [@10 minutes@] +]

Changed lines 36-38 from:
--> [every @500,000 database rows@] = [@10 minutes@]

to:
--> [@Every 500,000 database rows@] = [@10 minutes@]

Changed lines 34-38 from:
to:
Summary:

--> [every @500,000 database rows@] = [@10 minutes@]

Changed lines 3-4 from:
Database upgrades may occur during an install-over-the-top upgrade.  It is important for administrators to read this article to help plan their PaperCut upgrade.
to:
Database upgrades may occur during an install-over-the-top upgrade.  It is important for administrators to read this article to help plan their PaperCut upgrade.  A database upgrade will mean PaperCut must be taken off line for a few minutes and this article helps you understand this and mitigate the effect of expected downtime.
Changed lines 21-22 from:
!! Upgrade Planning
to:
!!How to estimate upgrade times (upgrade planning)
Changed lines 30-34 from:
Based on a typical system we estimate that the upgrade will take approximately 2 minutes for every 100,000 database rows in the database.  PaperCut versions 7.4 (or later) include database statistics information on the application About page.  These statistics include the total number of print logs and transaction logs, and can be used to calculate an estimate of the database upgrade time.

So for example, if the About page says you have a total of 500,000 rows (i.e. the print log count plus the transaction log count), then you should allow 10 minutes for the upgrade to complete.

to:
Based on a typical system we estimate that the upgrade will take approximately 2 minutes for every 100,000 database rows in the database.  PaperCut versions 7.4 (or later) include database statistics information on the application ''About'' page.  These statistics include the total number of print logs and transaction logs, and can be used to calculate an estimate of the database upgrade time.

So for example, if the ''About'' page says you have a total of 500,000 rows (i.e. the print log count plus the transaction log count), then you should allow 10 minutes for the upgrade to complete.

Changed lines 32-34 from:
So for example, if the About page says you have a total of 500,000 rows (i.e. the print log count plus the transaction log count), then you should allow 12 minutes for the upgrade to complete.

to:
So for example, if the About page says you have a total of 500,000 rows (i.e. the print log count plus the transaction log count), then you should allow 10 minutes for the upgrade to complete.

Added lines 1-2:
(:title Database Upgrades:)
December 12, 2007, at 04:45 AM by 218.214.136.161 -
Changed line 33 from:
''Categories:'' [[Category.Upgrading|+]]
to:
''Categories:'' [[Category.Upgrading|+]], [[!Databases]]
Changed lines 17-18 from:
'''IMPORTANT:  While the upgrade is in progress, it is important to not reboot the server or stop the PaperCut Application Server service.'''
to:
'''IMPORTANT:'''  While the upgrade is in progress, it is important to ''not'' reboot the server or stop the PaperCut Application Server service.
Changed lines 1-4 from:
Database upgrades may occur during a install-over-the-top upgrade.  It is important for administrators to read this article to help plan their PaperCut upgrade.

New features in PaperCut sometimes require new fields or tables in the application's database.  When a new version of PaperCut with database changes is installed, it will automatically upgrade the database without any interaction from the administrator.  The automatic upgrade occurs whether you are running the internal database or an external database like SQL Server or [=PostgreSQL=].
to:
Database upgrades may occur during an install-over-the-top upgrade.  It is important for administrators to read this article to help plan their PaperCut upgrade.

New features in PaperCut sometimes require new fields or tables in the application's database.  The install process will automatically upgrade the existing database without any interaction from the administrator.  The automatic upgrade occurs whether you are running the internal database or an external database like SQL Server or [=PostgreSQL=].
Changed lines 9-16 from:
# The required fields or tables are added.

# The new fields or tables are populated with data (if required by the given database changes).

# On the internal database, optimize the tables to ensure the system performs well with large data.

While these steps occur the application will be stopped.  However, you can monitor the progress of the upgrade by visiting the standard PaperCut URL in your web browser. e.g. http://papercutservername:9191/
to:
# New fields or tables are added.

# Any new fields or tables are populated with data (if required by the given database changes).

# On the internal database, the tables are optimized to ensure the system performs well with large data.

During this procedure you can monitor the progress by visiting the standard PaperCut URL in your web browser. e.g. http://papercutservername:9191/
Changed lines 21-22 from:
When a PaperCut update contains a database upgrade, the upgrade process will take longer to complete.  It is important to take this into account when planning the upgrade.
to:
When a PaperCut update contains a database upgrade (as referenced in the release notes), the upgrade process may take longer to complete.  It is important to take this into account when planning the upgrade on large networks.
Changed lines 3-4 from:
New features in PaperCut sometime require new fields or tables in the application's database.  When a new version of PaperCut with database changes is installed, PaperCut will automatically upgrade the database without any interaction from the administrator.  The automatic upgrade occurs whether you are running the internal database or an external database like SQL Server or [=PostgreSQL=].
to:
New features in PaperCut sometimes require new fields or tables in the application's database.  When a new version of PaperCut with database changes is installed, it will automatically upgrade the database without any interaction from the administrator.  The automatic upgrade occurs whether you are running the internal database or an external database like SQL Server or [=PostgreSQL=].
Added lines 32-33:

''Categories:'' [[Category.Upgrading|+]]
Changed lines 28-29 from:
Based on a typical system we estimate that the upgrade will take approximately 2 minutes for every 100,000 database rows in the database.  PaperCut versions 7.5 or later include database statistics information on the application About page.  These statistics include the total number of print logs and transaction logs, and can be used to calculate an estimate of the database upgrade time.
to:
Based on a typical system we estimate that the upgrade will take approximately 2 minutes for every 100,000 database rows in the database.  PaperCut versions 7.4 (or later) include database statistics information on the application About page.  These statistics include the total number of print logs and transaction logs, and can be used to calculate an estimate of the database upgrade time.
Added lines 1-2:
Database upgrades may occur during a install-over-the-top upgrade.  It is important for administrators to read this article to help plan their PaperCut upgrade.
Changed lines 26-29 from:
# The type of database (e.g. the internal database or an external database like SQL Server or [=PostgreSQL=].

Based on a typical system we have estimated that a database upgrade will take approximately 2 minutes for every 100,000 database rows in the PaperCut database.  PaperCut versions 7.5 or later include database statistics information on the application About page.  These statistics include the total number of print logs and transaction logs, and can be used to calculate an estimate of the database upgrade time.
to:
# The type of database (e.g. the internal database or an external database like SQL Server or [=PostgreSQL=]).

Based on a typical system we estimate that the upgrade will take approximately 2 minutes for every 100,000 database rows in the database.  PaperCut versions 7.5 or later include database statistics information on the application About page.  These statistics include the total number of print logs and transaction logs, and can be used to calculate an estimate of the database upgrade time.
Changed lines 3-12 from:
When an upgrade is performed the following steps occur:

# The database is backed up. This ensures that the system is recoverable if any unforeseen problems occur
.

# The required fields or tables are added to the database.

# The new fields or tables are populated with data (if required by
the given database changes)

# If running the default internal database, optimize the database
tables to ensure the system performs well with large data.
to:
When an upgrade is performed:

# The database is backed up. This ensures that the system is recoverable on an unforeseen problem.

# The required fields or tables are added
.

# The new fields or tables are populated with data (if required by the given database changes).

# On the internal database, optimize
the tables to ensure the system performs well with large data.
Changed lines 15-16 from:
'''IMPORTANT:  While the upgrade is in progress, it is important to not stop the reboot the server or stop the PaperCut Application Server service.'''
to:
'''IMPORTANT:  While the upgrade is in progress, it is important to not reboot the server or stop the PaperCut Application Server service.'''
Changed lines 9-10 from:
# The new fields/tables are populated with data (if required by the given database changes)
to:
# The new fields or tables are populated with data (if required by the given database changes)
Changed lines 1-2 from:
New features in PaperCut sometime require new fields or tables in the application's database.  When this new version with database changes is installed, PaperCut will automatically upgrade the database without any interaction from the administrator.  The automatic upgrade occurs whether you are running the internal database or an external database like SQL Server or [=PostgreSQL=].
to:
New features in PaperCut sometime require new fields or tables in the application's database.  When a new version of PaperCut with database changes is installed, PaperCut will automatically upgrade the database without any interaction from the administrator.  The automatic upgrade occurs whether you are running the internal database or an external database like SQL Server or [=PostgreSQL=].
Changed lines 1-2 from:
New features in PaperCut sometime require new fields or tables in the application's database.  When this new version with these database changes is installed, PaperCut will automatically upgrade the database without any interaction from the administrator.  The automatic upgrade occurs whether you are running the internal database or an external database like SQL Server or [=PostgreSQL=].
to:
New features in PaperCut sometime require new fields or tables in the application's database.  When this new version with database changes is installed, PaperCut will automatically upgrade the database without any interaction from the administrator.  The automatic upgrade occurs whether you are running the internal database or an external database like SQL Server or [=PostgreSQL=].
Added lines 1-29:
New features in PaperCut sometime require new fields or tables in the application's database.  When this new version with these database changes is installed, PaperCut will automatically upgrade the database without any interaction from the administrator.  The automatic upgrade occurs whether you are running the internal database or an external database like SQL Server or [=PostgreSQL=].

When an upgrade is performed the following steps occur:

# The database is backed up. This ensures that the system is recoverable if any unforeseen problems occur.

# The required fields or tables are added to the database.

# The new fields/tables are populated with data (if required by the given database changes)

# If running the default internal database, optimize the database tables to ensure the system performs well with large data.

While these steps occur the application will be stopped.  However, you can monitor the progress of the upgrade by visiting the standard PaperCut URL in your web browser. e.g. http://papercutservername:9191/

'''IMPORTANT:  While the upgrade is in progress, it is important to not stop the reboot the server or stop the PaperCut Application Server service.'''

!! Upgrade Planning

When a PaperCut update contains a database upgrade, the upgrade process will take longer to complete.  It is important to take this into account when planning the upgrade.

The time taken to perform a database upgrade is dependent on:
# The specs of the system running PaperCut.
# The size of the database (e.g. the number of print and transaction logs).
# The type of database (e.g. the internal database or an external database like SQL Server or [=PostgreSQL=].

Based on a typical system we have estimated that a database upgrade will take approximately 2 minutes for every 100,000 database rows in the PaperCut database.  PaperCut versions 7.5 or later include database statistics information on the application About page.  These statistics include the total number of print logs and transaction logs, and can be used to calculate an estimate of the database upgrade time.

So for example, if the About page says you have a total of 500,000 rows (i.e. the print log count plus the transaction log count), then you should allow 12 minutes for the upgrade to complete.

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on April 11, 2011, at 07:45 AM
Printable View   |   Article History   |   Edit Article