There are 2 offerings: 
a. An environment for 2 months with Cluster Uptime with 72 hours. 
b. An environment for 4 months with Cluster Uptime with 136 hours. 

The time assigned for each student is calculated as 8 hours per week. 

As an instructor you would have admin access over the workspace, you will also get permissions to create catalogs & manage permissions for the users. 

As an instructor you would have “can manage” Clusters/SQL warehouse permissions, while the students will have “can restart” permissions over the cluster & “can use” permissions over the SQL warehouse. 

1. What features are at my disposal as an instructor? 

As an instructor you will be able to access and manage student environments. 

For students there would be a restriction to create a personal/all-purpose compute cluster, SQL Warehouse, deploy DLT pipelines & use the Partner Connect feature. 

If you require additional time, you can let us know in advance, we can increase the lab uptime which would be available for an additional cost. 

You as an instructor have permissions to install the libraries, but you can always share the list of libraries to be pre-installed with us, for which we will take care at the backend & get them installed for you. 

The Databricks compute resources will be hosted on AWS. 

If you wish to host the Databricks compute resources on any other cloud platform, you can reach out to us & we will be able to help you with the custom request. It can be hosted on Azure & GCP as well, although there won’t be any difference in features available within Databricks workspace, but the cloud costs might be different. 

There are two concepts here: 

• Lab Uptime Hours: Lab uptime which would be the time for which students will have access to the Databricks Cluster or SQL Warehouse to perform operations. If the lab uptime is exhausted, the students won’t be able to access or perform operations using the lab cluster, but the data would be intact. If you wish to increase the lab uptime you can reach back to us. 
   

• Lab duration: Lab duration is the time for which the lab environment is  available for students. If the lab duration is exhausted, then students won’t be able to access the lab environment & the data will be lost. However, lab duration can be extended before it expires based on the advance request received. 

Example: If we consider that a semester is going to run for 2 months then students require a lab to be active for those months & we would set-up Lab duration according to that which would be 2 months. 

Now, suppose students have bi-weekly classes, each of 4 hours, so the total time expected by a student to work on Databricks Cluster/SQL Warehouse is 8 hours per week, so based on this the total uptime for the semester would be 72 hours (including a buffer)