Erin Dempster

Moving code from development to QA to UAT and eventually production can be a project in of itself. This is especially true when multiple projects might be across multiple repositories.

Deploying changes for a single database is easy on a team of 2 or 3. What happens when there are several databases being updated by a larger team, say five or more developers?

As a DBA, connecting to a database server on-premises is generally straightforward, especially in a company with a network infrastructure team. Over time, they have fine-tuned network configurations, so adding a new server works.

Moving database code from development to QA to UAT and eventually production can be a project in of itself. This is especially true when multiple projects might be across multiple repositories.

Developing database changes is just the beginning. Once the code has been committed to source control, moving code between environments can be cumbersome in a manual environment.

Developing database changes is just the beginning. Once the code has been committed to source control, moving code between environments can be cumbersome in a manual environment.

As a DBA, connecting to a database server on-premises is generally straightforward, especially in a company with a network infrastructure team. Over time, they have fine-tuned network configurations, so adding a new server works.

Moving code from development to QA to UAT and eventually production can be a project itself. This is especially true when there are multiple projects that might be across multiple repositories.

As a DBA, connecting to a database server on-premises is generally straightforward, especially in a company with a network infrastructure team. Over time, they have fine-tuned network configurations, so adding a new server works.

Moving code from development to QA to UAT and eventually production can be a project itself. This is especially true when there are multiple projects that might be across multiple repositories.

Getting data prepared for the ETL process into a data warehouse can be more than a task in itself. The ETL process may expect JSON files, but you can only get data in a CSV or XLSX file.

New to SQL Server 2016 (okay, it's a few years old already, but it still feels new) is Row Level Security, which allows database developers and architects to effectively lock down tables, giving users access to a defined subset of data in the table.

SQL Server 2019 has a number of new and exciting features for the BI world, including the Big Data Cluster Edition with HDFS and Spark being added to Microsoft's offering. This session will give an overview of these features, as well as a few demos.