Power BI, DAX | SQL Server | MS Access, VBA
DESIGN STANDARDS & CAPABILITIES

STANDARDIZE FOR
Easy Modifications
Developer Rotation
OPTIMIZE FOR
Speed
Future Back-end Upsizing
POWER BI
  • ETL extract, transform, load external and legacy data into the Query Editor
  • Star and Snowflake Relational Data Modeling Schemas
  • Dimension and Fact Separations
  • Custom metrics. Conditional formatting, striving for to balance data and white space
  • Slicers menus that toggle in visibility, conserving screen space for maximum focus
  •  Dashboards. DAX Data Analysis Expressions. Linear regression trend identification/quantification. Moving averages, time intelligence functions, KPI reporting, Segmenting and grouping data
  • Descriptive, diagnostic, predictive analytics. “ What if ” scenarios and forecast
  • Adhere to in place naming conventions
 
POWER BI CLOUD SERVICE
  • Publish reports to workspaces
  • Create dashboards with linked visualizations and cascading filters
  • Extract iframe code for inline web page embedding
  • Set permissions & refresh schedules
  • Row level security 
 
SQL SERVER
  • Create Cloud Server, databases, tables, views
  • Create and call stored procedures
  • Union Queries and complex queries with multiple joins and sub-queries
  • T-SQL Transact CRUD commands to Create, Read, Update or Delete
  • Utilize SQL Views to limit data exposed to the front-end application 

 

MICROSOFT ACCESS
  • Tables have primary key
  • Commonly queried columns are indexed
  • Field Size not larger than needed
  • Relationships diagram present, Table relationships defined, Referential integrity enforced
  • Soft Code- Store Logos paths, file paths, user permissions in tables; Allow authorized users to edit
  • Switchboard Form /Main Navigation Form: Queries and reports refer to forms for dynamic criteria (vs. criteria saved in copies of them parameter dialog boxes)
  • Naming Conventions in place and followed
DAX and MICROSOFT POWER BI
  • Utilize Measures over calculated columns when possible
  • Maintain organized measure’s tables
  • Adhere to naming conventions
  • Indent for readability
  • Add comments so the next developer can easily follow
  • VAR: Use variables internally when possible so the next developer can easily follow
 
VBA and MICROSOFT ACCESS 
  • Compile Code
  • Use option explicit to require variable declaration
  • Password protected
  • Comment procedures with an explanation
  • Indent code blocks for easy recognition
  • Error handling utilized
  • Memory Management: Close Recordset variables; Set database variables to nothing
  • External Application Automation (i.e. Outlook, Excel): Use late binding