eva-qa-database
Query and analyze the Eva QA database using PowerShell functions. Use when working with Eva sessions, committee reports, meeting notices, or any Eva application data in the QA environment.
When & Why to Use This Skill
The Eva QA Database skill enables seamless interaction with the Eva application's database environments through specialized PowerShell functions. It facilitates secure data retrieval and insertion across QA, DEMO, and UAT environments, allowing users to analyze legislative sessions, committee reports, and meeting notices while maintaining strict safety protocols for data integrity.
Use Cases
- Retrieving and verifying current legislative session data or recent committee reports during the QA testing phase.
- Inserting controlled test records into the database to simulate application behavior and validate new features.
- Exploring database schemas and table structures using metadata queries to troubleshoot 'Invalid object' or 'Invalid column' errors.
- Performing cross-environment data analysis (QA vs. UAT) to ensure data consistency and successful environment synchronization.
| name | eva-qa-database |
|---|---|
| description | Query and analyze the Eva QA database using PowerShell functions. Use when working with Eva sessions, committee reports, meeting notices, or any Eva application data in the QA environment. |
| author | michigan-senate |
| version | "1.0" |
| environments | "QA, DEMO, UAT, Local" |
Eva QA Database Skill
This skill provides access to the Eva application database in the QA environment using PowerShell functions.
Available Functions
Query Data (SELECT)
Use Invoke-EvaSql for SELECT queries that return data:
Invoke-EvaSql -Query "SELECT * FROM sessions" -Environment QA
Security Note: Invoke-EvaSql is restricted to SELECT queries only. UPDATE, DELETE, DROP, and other dangerous operations are blocked for safety.
Insert Data (INSERT)
Use Invoke-EvaSqlNonQuery for inserting new records:
Invoke-EvaSqlNonQuery -Query "INSERT INTO sessions (Name, StartDate) VALUES ('Test Session', GETDATE())" -Environment QA
Security Note: Invoke-EvaSqlNonQuery is restricted to INSERT queries only. UPDATE and DELETE operations are blocked to prevent accidental data modification.
Environment Options
QA(default) - Eva_QA database on tvmwsqls01DEMO- Eva_DEMO database on uvmwsqls01UAT- Eva_UAT database on uvmwsqls01Local- Local development database
Common Tables
See DATABASE-SCHEMA.md for complete schema information.
Core Tables
sessions- Legislative sessionsCommitteeReports- Committee report dataCommitteeMeetingNotices- Meeting noticesCommitteeMeetingAgendaData- Agenda itemsCalendarCommitteeEdits- Calendar edits
Usage Examples
See COMMON-QUERIES.md for frequently used queries.
Get Current Session
Invoke-EvaSql -Query "SELECT * FROM sessions WHERE IsCurrentSession = 1" -Environment QA
Get Recent Committee Reports
Invoke-EvaSql -Query "SELECT TOP 10 * FROM CommitteeReports ORDER BY Created DESC" -Environment QA
Find Tables by Pattern
Invoke-EvaSql -Query "SELECT TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME LIKE '%pattern%'" -Environment QA
Best Practices
- Always specify the environment - Even though QA is default, be explicit
- Use TOP for exploration - Limit results when exploring tables
- Check schema first - Query INFORMATION_SCHEMA to understand table structure
- Handle errors - The functions automatically display SQL errors
- Use transactions carefully - For updates, verify with SELECT first
Connection Details
Connection strings are managed in the EvaSql.psm1 module. See CONNECTION-STRINGS.md for details.
Troubleshooting
Error: "Invalid object name"
- Table name might be wrong or not exist
- Query INFORMATION_SCHEMA.TABLES to find correct name
Error: "Invalid column name"
- Column doesn't exist in table
- Query INFORMATION_SCHEMA.COLUMNS to see available columns
Connection timeout
- VPN connection might be down
- Server might be unreachable