Moving or Copying a TariffShark Database

[Updated August 15, 2024]

Sometimes it is necessary to move or copy a TariffShark database from one server to another.  You might need to do this if you’re setting up a new production environment or refreshing a test environment with current production data.  This blog article describes the best practice procedure for cloning a TariffShark database.

  1. Backup the database you are copying using the SQL Server utility for this purpose.
  2. Restore the database to a different SQL Server Instance and/or different database, again, using the SQL Server utility for this purpose.
  3. The Audit table tracks web service method calls and responses for a TariffShark application server (which is done strictly for debugging reasons).  When establishing a new database, this data has little meaning when copied from another database.  As an optional step you may choose to TRUNCATE the Audit table.
  4. The Relationships table must be rebuilt in the restored database.  Run the following script statements in order to do this:
    USE […Name of the TariffShark Database…]
    GO
    EXEC admin.RebuildRelationships
    GO
  5. TariffShark Tiger is able to distinguish PROD environments from TEST ones.  In a TariffShark Tiger installation where PROD and TEST environments have been distinguished as such, your TEST environment will look like a PROD environment after the database restore.  In order to restore your TEST environment to “test” status, open a web browser and enter the following URL into the address bar:
    http[s]://<test_application_server_url>/Services/SetProduction.ashx?value=false

If you ever need to restore a TariffShark database, follow the procedure outlined above.  If you would like to know more about TariffShark databases or if you have any other questions, please comment below or contact TariffShark Support.

eTariff FTRV Level Associations

FERC’s eTariff rules allow you to associate a tariff record you are submitting with a previously filed tariff record.  In TariffShark terms, a Filed Tariff Record Version (FTRV) you are preparing to submit may be associated with an FTRV from an earlier Filing.  This article will explain why you might want to associate two FTRVs and how to do this in TariffShark.

An FTRV association tells FERC (a) to ignore the earlier-filed FTRV as you are no longer proposing that TRV for consideration and (b) to use the latter-filed one as a replacement proposal.  Upon OSEC acceptance of the second FTRV, FERC assigns a status of OBE (overtaken by events) to the first one (if it is still pending before the Commission).  The most common scenario where it would be appropriate to associate one FTRV with another is when filing a corrected FTRV (generally done in an amendment-type filing).  In this situation, the latter-filed FTRV is clearly a replacement for the earlier-filed one.

In TariffShark, associating an FTRV with another one can be done easily from the Update Filed Tariff Record Version screen.

  1. Open the Filing Details screen for the Filing you are preparing to submit to FERC.
  2. On the Tariff Record Versions tab, select the desired FTRV and click the Update FTRV command in the SmartBar (shown below), which will open the Update Filed Tariff Record Version screen.
  3. On the Update Filed Tariff Record Version screen, click the ellipsis button next to the Associated With field (shown below) to select an earlier-filed FTRV to which an association should be made.
  4. In the resulting pop-up form (shown below), (a) select the earlier Filing, (b) then select the earlier-filed FTRV in the grid, and (c) then click the Select button.
  5. Back on the Update Filed Tariff Record Version screen, click the Update button.

TariffShark Validations

Seems easy enough, right?  Well, the vanilla case described above is pretty straightforward.  However, there are more complex scenarios where it may or may not be appropriate to make an FTRV level association.  TariffShark does not pretend to understand all of the regulatory nuances surrounding the filing of tariff records.  Instead, it issues validation warnings in order to make you aware of opportunities to associate FTRVs and allows you to decide if it’s appropriate or not.

There are several validations in TariffShark that relate to FTRV level associations and most of these are very specific.  However, detailed below are the general purpose warnings.  Note that FTRV FERC Response (which describes the status of an FTRV) plays a big part in these validations.  Therefore, it is very important that you keep your FTRV FERC Response values accurately updated.

Validation R045

Filed Tariff Record Version (FTRV) “” is associated with another FTRV whose FERC Response is “Pending”. If the associated record has a status of “Pending” at FERC, submitting this Filing will cause the associated record’s status in the eTariff Viewer to become OBE (overtaken by events). Proceed with caution as this may not be what you intend.

Explanation of R045

If you have associated an FTRV with a Pending FTRV, this message appears.  In the vanilla case where you are submitting an amended FTRV, you would expect to see this validation warning.

Validation R046

Filed Tariff Record Version (FTRV) “” is not associated with another FTRV, yet one or more “Pending” FTRVs exist. If you intend to submit this FTRV as a replacement for one of the pending FTRVs, then you must associate this FTRV with the one you wish to replace.

Explanation of R046

If you have not associated an FTRV with another FTRV and one or more Pending FTRVs are present, this message appears.

Validation R047

[1] Filed Tariff Record Version (FTRV) “” is associated with another FTRV. [2] Tariff Record “” has child Tariff Records. Submitting this Filing will cause the associated record to become moot and its status in the eTariff Viewer to become OBE (overtaken by events). This automatic update in FERC’s software cascades to child Tariff Records also pending at FERC from earlier Filings. Under certain circumstances, this causes the child records to disappear…as if they hadn’t been filed. Proceed with caution!

Explanation of R047

The disappearance of child tariff records in FERC’s system happened to a TariffShark customer in 2010 after submitting a baseline eTariff filing followed shortly thereafter by a subsequent filing.  A complex combination of circumstances caused the child tariff records to disappear and such circumstances are not likely to be reproduced.  All the same, we felt it was prudent for TariffShark to warn eTariff filers of the potential issue.

If you would like to know more about FTRV-level associations or if you have any other questions, please comment below or contact TariffShark Support.

Tariff Record Version (TRV) Queue Processing

Tariff Record Version (TRV) Queue Processing runs automatically when TariffShark is running.  It is responsible for converting section-based and sheet-based Tariff Record Versions’ marked content edited in Microsoft Word into marked DOC, clean RTF, marked PDF, clean PDF, and plain text formats.  To make it unobtrusive, the work is done in the background.  To make it as quick and efficient as possible, the work is distributed across all logged in TariffShark users.

A section-based or sheet-based TRV is automatically submitted for document processing when a user saves the TRV’s content in Word.  Once submitted, it waits in a line (or queue) behind other TRVs that need to be processed.

Once in line, each TRV has up to three (3) attempts to finish processing successfully.  TRV queue processing status can be monitored from the Dashboard (for the context company).  A TRV that failed queue processing (one with zero retries left) can be re-submitted for processing from the “Failed Processing” tab on the Dashboard.  All document processing associated with a TRV queue item is performed on the client computer.   Files are temporarily saved in the temp folder and, once all content is ready, the data is permanently saved on the server.

As a user, you can manage the frequency at which TariffShark checks the queue for new content to be processed by adjusting the “Queue Processing Interval” setting.  Valid values are integer numbers between 5 and 300 (seconds).  If there are a lot of TRVs in the queue and you’d like them processed as quickly as possible, a low number of seconds keeps your computer busy processing TRVs.  If you don’t want your computer slowed down by processing TRVs, use a higher number of seconds, but be advised that the TRV Queue will be cleared out more slowly.  To learn how to change the Queue Processing Interval, check out the blog article entitled TariffShark Document Processing.

Automated Queueing of TRVs

If a TRV’s Document Layouts use Header and/or Footer Templates that leverage TariffShark data fields, any change in the fields’ values automatically submits the TRV for document processing.  Further, if a Header or Footer Template is updated, all TRVs that use Document Layouts that leverage the updated Template will automatically be submitted for processing.  Use great caution when updating Header and Footer Templates because if they’re widely used, many, many TRVs could be inserted into the TRV Queue.

No doubt, this is a complex topic…and we would be happy to clarify it further.  Simply comment below or contact TariffShark Support.

Does My eTariff Filing Have to Include Tariff Records?

In last week’s blog article, eTariff Filing Level Associations, we introduced nine broad filing type categories.  This article will use the same broad categories to answer the question “does my eTariff filing have to include tariff records”?

Normal – A “normal” filing generally initiates a statutory action against an existing eTariff.  As such, proposed changes to an electronic FERC tariff would be made by submitting tariff records.

New – A “new” filing establishes a new Tariff Id (FERC’s term for what TariffShark calls a Tariff Database).  This type of filing must include tariff records.

Refiled – Like a “new” filing, a “refiled” filing establishes a new Tariff Id.  This type of filing must include tariff records.

Compliance – The circumstances surrounding a “compliance” type filing vary greatly.  Some compliance filings will include tariff records and some will not.

Amendment – An “amendment” filing proposes changes to an earlier eTariff filing pending before the Commission.  What’s being amended in a amendment filing are tariff records.  Therefore, this type of filing must include tariff records.

Motion – A “motion” filing motions into effect tariff record from an earlier eTariff filing.  Therefore, tariff records must be included in a motion filing. In order to add tariff records from an earlier filing to a “motion” filing, the Filed Tariff Record Versions in the earlier filing must have a FERC Response of Suspended”.

Withdraw – The sole purpose of a “withdraw” type filing is to withdraw an earlier eTariff filing pending before the Commission.  A withdraw type filing must not include tariff records.

Report – Similar to an “amendment” filing, a “report” filing is used to supplement the record of an earlier eTariff filing pending before the Commission.  Unlike the “amendment” type, however, a report type consists solely of attachments.  Statutory tariff records are not allowed in this type of filing.  It is valid, however, to include pro forma tariff records within a “report” filing.

Cancellation – A “cancellation” filing proposed to cancel an entire Tariff Id (FERC’s term for what TariffShark calls a Tariff Database).  A cancellation filing must include a single tariff record, which carries the proposed effective date of the cancellation.

To summarize…

Type of Filing Includes Tariff Records?
Normal Always
New Always
Refiled Always
Compliance Sometimes
Amendment Always
Motion Always
Withdraw Never
Report Pro Forma Only
Cancellation Exactly 1

If you would like to know more including tariff records in your eTariff filings or if you have any other questions, please comment below or contact TariffShark Support.