Fast Times at SQL Server High Data Management Inside a NASCAR Race Team Andy Korczynski - Red Bull Racing

Overview What is NASCAR? What is NASCAR? Typical NASCAR team organization Typical NASCAR team organization How does SQL Server help? How does SQL Server help? Possible SQL Server architectures Possible SQL Server architectures NASCAR is highly competitive NASCAR is highly competitive No application demos, code samples, or specific details on architecture No application demos, code samples, or specific details on architecture

Overview of NASCAR National Association for Stock Car Auto Racing National Association for Stock Car Auto Racing NASCAR Sprint Cup Series (NSCS) NASCAR Sprint Cup Series (NSCS) NASCAR Nationwide Series (NNS) NASCAR Nationwide Series (NNS) NASCAR Craftsman Truck Series (NCTS) NASCAR Craftsman Truck Series (NCTS) Various regional series Various regional series NSCS has 36 races in a season NSCS has 36 races in a season

Overview of NASCAR (cont) Roughly 18 teams compete each week Roughly 18 teams compete each week ~$15 Million to field a car for the year ~$15 Million to field a car for the year ~$5 Million in purse money per race ~$5 Million in purse money per race Most teams field 2+ cars Most teams field 2+ cars Toyota, Chevy, Dodge, and Ford Toyota, Chevy, Dodge, and Ford 8 Million TV viewers 8 Million TV viewers Events can attract 100,000+ people Events can attract 100,000+ people

Cup Car Specs Carbureted V8 Engine Carbureted V8 Engine ~750 HP ~750 HP 4 speed manual transmission 4 speed manual transmission ~3400 lbs ~3400 lbs 3-4 MPG 3-4 MPG Unleaded Gasoline Unleaded Gasoline Power Steering! Power Steering!

Cup Team Overview Approximately 100 employees per car Approximately 100 employees per car Teams employ engineers Teams employ engineers Track side organization Track side organization Crew Chief Crew Chief Race Engineer Race Engineer Car Chief Car Chief Mechanics Mechanics Pit Crew Pit Crew

How Can SQL Server Help? Document Management Document Management Enterprise Resource Planning (ERP) Enterprise Resource Planning (ERP) Manufacturing Resource Planning (MRP) Manufacturing Resource Planning (MRP) Race car setup data management Race car setup data management Race car data systems management Race car data systems management Simulation data management Simulation data management Workflow management Workflow management

Document Management Practice/Race Reports Practice/Race Reports Car design/CAD management Car design/CAD management Technical Bulletins Technical Bulletins Timing and Scoring Reports Timing and Scoring Reports Best practices Best practices

Race Car Data Systems Most teams use Pi Data Systems for sensor data collection Most teams use Pi Data Systems for sensor data collection Typical setup involves 30+ sensors Typical setup involves 30+ sensors A practice outing produces about 10-15MB of data A practice outing produces about 10-15MB of data Data must be disseminated to track and shop personnel as quickly as possible Data must be disseminated to track and shop personnel as quickly as possible

Race Car Setup Tire data Tire data Shock data Shock data Vehicle setup information Vehicle setup information Sensor Data Sensor Data Practice vehicle outing/run data Practice vehicle outing/run data Race log Race log Driver feedback Driver feedback

Simulation Data Rig data results Rig data results Computer simulation results Computer simulation results Must be fed with real data Must be fed with real data Results must be fed back to central database Results must be fed back to central database

SQL Server to the Rescue! All data is stored in SQL Server All data is stored in SQL Server Security Security Provides an easy way to back up all critical data Provides an easy way to back up all critical data Provides replication services to maintain a high level of data availability Provides replication services to maintain a high level of data availability

SQL Server Replication Snapshot replication Snapshot replication Provides initial set of data for merge replication Provides initial set of data for merge replication Good for infrequently changing data Good for infrequently changing data Merge replication Merge replication Good for server to client applications Good for server to client applications Transactional replication Transactional replication Ideally suited for server to server Ideally suited for server to server

Merge Replication Snapshot replication used to populate initial data Snapshot replication used to populate initial data Can be based on a push or pull system Can be based on a push or pull system Can create multiple publications from the same database Can create multiple publications from the same database Based on a Publisher/Subscriber system Based on a Publisher/Subscriber system Can deal with schema changes Can deal with schema changes

Merge Replication Types (Push) Publisher (Server) connects to the Subscriber (client) Publisher (Server) connects to the Subscriber (client) Works with SQL Server Express Works with SQL Server Express Can bog down server if there are a lot of clients (each client is synchronized via a SQL Server Agent job) Can bog down server if there are a lot of clients (each client is synchronized via a SQL Server Agent job)

Merge Replication Types (Pull) Subscriber (client) initiates connection to Publisher (client) Subscriber (client) initiates connection to Publisher (client) Not available with SQL Express (No SQL Server Agent) Not available with SQL Express (No SQL Server Agent) Can use anonymous subscriptions and write your own synchronization agent Can use anonymous subscriptions and write your own synchronization agent

Merge Replication Limits 256 Articles 256 Articles Limits the number of stored procedures Limits the number of stored procedures Creating multiple publications can be hazardous! Creating multiple publications can be hazardous! 246 Columns in a table 246 Columns in a table Think vertical table design Think vertical table design 1024 Bytes for a column used in a row filter 1024 Bytes for a column used in a row filter

Central Race Team Scenario SQL Server cluster at the main facility SQL Server cluster at the main facility Local non-travelling clients connect directly to cluster Local non-travelling clients connect directly to cluster Travelling clients run SQL Express and connect periodically Travelling clients run SQL Express and connect periodically Information is available and updated throughout the race Information is available and updated throughout the race Allows everyone to be a “backseat” crew chief Allows everyone to be a “backseat” crew chief

The Hauler Scenario This is where the race team lives on the weekends This is where the race team lives on the weekends Local Server SQL that can act as publisher and subscriber Local Server SQL that can act as publisher and subscriber Local SQL provides faster replication times for local clients Local SQL provides faster replication times for local clients Allows replication within a team even if connection to shop goes down Allows replication within a team even if connection to shop goes down

SQL Server Compact Can participate in replication Can participate in replication Great for small devices used for data entry Great for small devices used for data entry Tire data Tire data Trackside weather information Trackside weather information GPS enabled devices GPS enabled devices

In Conclusion SQL Server in racing is exciting!!!! SQL Server in racing is exciting!!!! New SQL Server Filestream data type will make working with large data types easier New SQL Server Filestream data type will make working with large data types easier Technology and data sharing really do help win races Technology and data sharing really do help win races THANK YOU!