ge-aerospace/shopdb
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
e2e7cb146657fbf6b0ddd2dd230d6a523a9a3792
shopdb/docs/MIGRATION_QUICK_REFERENCE.md
cproudlock 4bcaf0913f Complete Phase 2 PC migration and network device infrastructure updates 
This commit captures 20 days of development work (Oct 28 - Nov 17, 2025)
including Phase 2 PC migration, network device unification, and numerous
bug fixes and enhancements.

## Major Changes

### Phase 2: PC Migration to Unified Machines Table
- Migrated all PCs from separate `pc` table to unified `machines` table
- PCs identified by `pctypeid IS NOT NULL` in machines table
- Updated all display, add, edit, and update pages for PC functionality
- Comprehensive testing: 15 critical pages verified working

### Network Device Infrastructure Unification
- Unified network devices (Switches, Servers, Cameras, IDFs, Access Points)
  into machines table using machinetypeid 16-20
- Updated vw_network_devices view to query both legacy tables and machines table
- Enhanced network_map.asp to display all device types from machines table
- Fixed location display for all network device types

### Machine Management System
- Complete machine CRUD operations (Create, Read, Update, Delete)
- 5-tab interface: Basic Info, Network, Relationships, Compliance, Location
- Support for multiple network interfaces (up to 3 per machine)
- Machine relationships: Controls (PC→Equipment) and Dualpath (redundancy)
- Compliance tracking with third-party vendor management

### Bug Fixes (Nov 7-14, 2025)
- Fixed editdevice.asp undefined variable (pcid → machineid)
- Migrated updatedevice.asp and updatedevice_direct.asp to Phase 2 schema
- Fixed network_map.asp to show all network device types
- Fixed displaylocation.asp to query machines table for network devices
- Fixed IP columns migration and compliance column handling
- Fixed dateadded column errors in network device pages
- Fixed PowerShell API integration issues
- Simplified displaypcs.asp (removed IP and Machine columns)

### Documentation
- Created comprehensive session summaries (Nov 10, 13, 14)
- Added Machine Quick Reference Guide
- Documented all bug fixes and migrations
- API documentation for ASP endpoints

### Database Schema Updates
- Phase 2 migration scripts for PC consolidation
- Phase 3 migration scripts for network devices
- Updated views to support hybrid table approach
- Sample data creation/removal scripts for testing

## Files Modified (Key Changes)
- editdevice.asp, updatedevice.asp, updatedevice_direct.asp
- network_map.asp, network_devices.asp, displaylocation.asp
- displaypcs.asp, displaypc.asp, displaymachine.asp
- All machine management pages (add/edit/save/update)
- save_network_device.asp (fixed machine type IDs)

## Testing Status
- 15 critical pages tested and verified
- Phase 2 PC functionality: 100% working
- Network device display: 100% working
- Security: All queries use parameterized commands

## Production Readiness
- Core functionality complete and tested
- 85% production ready
- Remaining: Full test coverage of all 123 ASP pages

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 20:04:06 -05:00

4.8 KiB
Raw Blame History

Database Migration - Quick Reference

Date: 2025-11-06 Status: Design Finalized

What We're Doing

Consolidating PCs into machines table + adding communications, compliance, and warranty tracking.

New Tables (7)

  1. comstypes (8 cols) - Communication type lookup (IP, Serial, Network, etc.)
  2. communications (9 cols) - Universal comm tracking with generic address field
  3. compliance (14 cols) - Security/compliance data from inventory.xlsx
  4. compliancescans (5 cols) - AV/malware scan log
  5. warranties (5 cols) - Simple warranty tracking (name + expiration)
  6. relationshiptypes (5 cols) - Machine relationship types (Dualpath, Controlled By, etc.)
  7. machinerelationships (6 cols) - Machine-to-machine relationships tracking

Modified Tables (2)

  1. machines - Add 9 PC-related columns (hostname, serialnumber, osid, etc.)
  2. businessunits - Add 2 liaison fields (liaisonname, liaisonsso)

Renamed Tables (1)

  1. pcstatus → machinestatus - Consistent naming

Deprecated Tables (4)

Drop after 30-day testing:

  1. pc
  2. pc_comm_config
  3. pc_network_interfaces
  4. pctype

Key Design Decisions

✅ Generic address field - One field for IP/COM/USB/etc (determined by comstypeid) ✅ Simplified warranties - Just name + expiration date ✅ Liaison in businessunits - No separate liaisons table ✅ Unified machine types - PC types added to machinetypes ✅ Vendor FK - compliance.managedbyvendorid → vendors table ✅ Minimal audit - Removed unnecessary dateadded/lastupdated fields ✅ Machine relationships - Generic table for dualpath, PC-to-machine control, future clusters

Migration Volumes

Source Destination Records
pc table machines 277
machines.ipaddress1/2 communications ~266
pc_network_interfaces communications ~277+
pc_comm_config communications ~100+
pc warranties warranties ~277+
Total ~650+ comms

Phase 1 Scripts (Ready to Create)

  1. Create communications infrastructure
  2. Extend machines table
  3. Create PC machine types
  4. Create warranty infrastructure
  5. Create compliance infrastructure
  6. Extend businessunits table
  7. Rename pcstatus table
  8. Create machine relationships infrastructure

Time: ~25 minutes Reversible: Yes

machines Table Final Structure (21 columns)

  1. machineid (PK)
  2. machinetypeid (now includes PC types!)
  3. machinenumber
  4. alias
  5. hostname (NEW - for PCs)
  6. serialnumber (NEW)
  7. loggedinuser (NEW - for PCs)
  8. modelnumberid
  9. controllertypeid (NEW - for CNC machines)
  10. controllerosid (NEW - controller OS, uses operatingsystems table)
  11. osid (NEW - for PCs, uses operatingsystems table)
  12. machinestatusid (NEW - renamed from pcstatusid)
  13. businessunitid
  14. printerid
  15. mapleft
  16. maptop
  17. isactive
  18. islocationonly
  19. machinenotes
  20. lastupdated (NEW)
  21. dateadded (NEW)

Key Design: Both PC OS and Controller OS use the same operatingsystems table!

Removed: pctypeid, isvnc, requires_manual_machine_config, ipaddress1, ipaddress2

communications Table Structure (9 columns)

  1. comid (PK)
  2. machineid (FK)
  3. comstypeid (FK)
  4. address (VARCHAR - universal: IP, COM1, eth0, etc.)
  5. port (for IP types)
  6. macaddress (for network types)
  7. description
  8. settings (JSON - type-specific config)
  9. isactive

compliance Table Structure (15 columns)

  1. complianceid (PK)
  2. machineid (FK)
  3. ongenetwork
  4. gecoreload
  5. assetcriticality
  6. cuidataclassification
  7. dodassettype
  8. dodassetsubtype
  9. otenvironment
  10. managedbyvendorid (FK to vendors)
  11. changerestricted
  12. jumpbox
  13. mft (Managed File Transfer)
  14. notes
  15. isactive

warranties Table Structure (5 columns)

  1. warrantyid (PK)
  2. machineid (FK)
  3. warrantyname
  4. enddate
  5. isactive

relationshiptypes Table Structure (5 columns)

  1. relationshiptypeid (PK)
  2. relationshiptype ('Dualpath', 'Controlled By', 'Controls', etc.)
  3. description
  4. isbidirectional (1 for symmetric, 0 for directional)
  5. isactive

machinerelationships Table Structure (6 columns)

  1. relationshipid (PK)
  2. relationshiptypeid (FK)
  3. machineid1 (FK to machines)
  4. machineid2 (FK to machines)
  5. notes
  6. isactive

Key Feature: Both machines and PCs are in machines table, so any machine can relate to any other machine.

Example:

  • Machines 2001 & 2002 are dualpath (relationshiptypeid=1)
  • Both controlled by PC 500 (relationshiptypeid=2)

Next Step

✅ Create Phase 1 SQL Scripts (8 scripts + 8 rollback scripts)

See DATABASE_MIGRATION_FINAL_DESIGN.md for complete specification.

Reference in New Issue View Git Blame Copy Permalink