Development ResourcesHRFocus internal library

Database schemas · Internal confidential

Understand the three core databases from one trusted workspace.

Download the scripted HRDB/MyFocus, PayrollDB, and CareerFocusDB definitions for dependency tracing, comparisons, tests, tax and leave analysis, and implementation planning.

Download all schemas Installation instructions Markdown guide

Choose a package

Schema downloads

Use the combined package when tracing shared or cross-database behaviour.

Download checksum manifest
Recommended

All core schemas

HRDB, PayrollDB, and CareerFocusDB in one correctly separated workspace.

Objects
10,107
Size
15.0 MB
Download combined ZIP
Parent schema

HRDB / MyFocus

Employee, compensation, organisation, workflow, notifications, Report Portal, and leave calculation definitions.

Objects
4,993
Size
6.6 MB
Download HRDB
Payroll and tax

PayrollDB

Payroll processing, tax calculation, tax configuration, reporting, and current HRDB-linked view definitions.

Objects
4,404
Size
7.6 MB
Download PayrollDB
CareerFocus

CareerFocusDB

CareerFocus definitions and shared platform objects used for comparison with the MyFocus parent implementation.

Objects
710
Size
0.8 MB
Download CareerFocusDB

Before extraction

Verify the download

Compare the calculated SHA-256 value with the package manifest. A mismatch means the file must not be used.

PowerShell
$zip = '.\HRFocus-Database-Schemas-All.zip'
$manifest = Import-Csv '.\Database-Schema-Package-Manifest.csv'
$expected = ($manifest | Where-Object Package -eq (Split-Path $zip -Leaf)).SHA256
$actual = (Get-FileHash -Algorithm SHA256 -LiteralPath $zip).Hash
if ($actual -ne $expected) { throw 'Database schema package checksum mismatch.' }

Published SHA-256 values

All schemas
D903DED98A51962CCCF5485E8B2A948F3CB49C9D97D3AEE98C8AEEE15DCB83D7
HRDB
D60AD6F17FAE5B3A618CC93B5F45049301332B59BBE9E89D12FBACB6F286E605
PayrollDB
EAEDD2692878E5AD99549F4B25C31ABD555DE4D5D61EF196887F31647CC999D3
CareerFocusDB
FDDF410193D2CBF91B5981C3E8D71B07FAA67F7C4E031D66BDAED54C0482FD76

Developer setup

Install as a database analysis project

Keep the databases separate and open their common parent folder as the workspace.

  1. Download and verifyDownload the combined ZIP and checksum manifest, then complete the verification above.
  2. Create a project folderUse a dedicated local folder such as C:\Development\HRFocus-Databases, outside an application repository.
  3. Extract the bundleExpand the ZIP into the project folder. Do not merge identically named objects from different databases.
  4. Open the common rootOpen HRFocus-Databases in Codex or the approved editor so skills can trace cross-database references.
  5. State authority and scopeTell the task which database is primary. HRDB/MyFocus is the parent unless the work is specifically PayrollDB or CareerFocusDB.
PowerShell
$projectRoot = 'C:\Development\HRFocus-Databases'
New-Item -ItemType Directory -Path $projectRoot -Force | Out-Null
Expand-Archive -LiteralPath '.\HRFocus-Database-Schemas-All.zip' `
    -DestinationPath $projectRoot -Force
Expected project structure 
HRFocus-Databases/
├── HRDB/
├── PayrollDB/
└── CareerFocusDB/

Codex and skill context

Use the schemas in analysis and implementation work

Include the schema root, authority, comparison boundary, and whether the task is analysis-only.

Tax calculation

Use PayrollDB as the primary schema and HRDB only for cross-database dependencies. Trace the tax calculation entry procedure, all called functions and procedures, and every tax table read or written. Analyse only and cite exact files and lines.

Shared platform comparison

Compare the Report Portal definitions in HRDB, PayrollDB, and CareerFocusDB. Treat HRDB/MyFocus as the parent implementation and report material differences without changing files.

Database change package

Use $build-hrfocus-database-package with these schema definitions as the baseline. Create only the approved changes as an ordered, rerunnable SQL Server 2016 package with verification and rollback guidance.

Important deployment boundary

Do not deploy a schema snapshot as a database upgrade.

The ZIPs describe current object definitions. They are not ordered migration packages, do not contain rollback logic, and may contain objects that are intentionally different between solutions.

  1. Compare the requested change with the correct database baseline.
  2. Create the smallest approved deployment package in dependency order.
  3. Make scripts rerunnable and SQL Server 2016-compatible.
  4. Test against a non-production database, including calculation regression cases.
  5. Review permissions, transactions, rollback, locking risk, and verification evidence before production.

Hub publication

Deploy this website to internal IIS

The governed source includes these pages, packages, manifests, tools, and all existing Development Resources content.

1

Build and verify

Run the website packager from the hub source. Verify the generated SHA-256 manifest before extraction.

Download packaging script
2

Stage and compare

Extract the deployment ZIP to a staging folder. Back up the current site and compare staged files with the IIS target before copying.

3

Configure IIS

Use an internal IIS application with Static Content and ASP.NET 4.8. Keep Windows/internal authentication in place and retain the included web.config.

4

Permissions and QA

If Admin is enabled, apply only the documented application-pool permissions. Test this Databases page, every ZIP, checksums, search, filters, and administration.

Build the deployment archive from the governed hub root
& '.\00 Administration\006 - Package Development Resources Website.ps1'
& '.\00 Administration\Validate-DeveloperResources.ps1'

# Output:
# .\04 Templates and Tools\Website Deployment\Packages\
#   HRFocus-Development-Resources-Website.zip
#   Website-Deployment-Package-Manifest.csv

Deployment scope: Copy the contents of the ZIP’s top-level DeveloperResources folder into the IIS application root. This publishes the resource website; it does not change any SQL Server database.

Next maturity step

Move the definitions into one private database repository.

Use one repository with separate HRDB, PayrollDB, and CareerFocusDB SQL projects. Establish a reviewed snapshot baseline first, then add SQL Server 2016 builds, explicit cross-database references, pull-request review, drift detection, and regression tests for critical tax and leave calculations. Automated database extracts should open a branch or pull request; they should never overwrite the reviewed main branch.