Rick Lowe

Indexing has a massive impact on performance in both SQL Server and PostgreSQL, and some aspects work much the same in both platforms. But there are differences that can trip up experienced SQL Server DBAs as they start working with PostgreSQL. This session will drill into some some of these...

Most of us have heard that query hints should not be used very often in SQL Server. That said, how often do things actually break if we do use a few NOLOCK hints?

SQL Server is a huge product, with many different places a DBA can go to look for information on how the server is performing. So many in fact that they can often overlap, which sometimes makes it hard to understand why tackling a new tool is worth the effort.

Despite the fact that SQL Server Availability Groups are built on top of a stack of rather complex technology, over the years things have gotten to the point where getting an AG up and running for a simple two-node HA setup is not as intimidating for most DBAs as it may have been in the early days.

SQL Server is a huge product, with many different places a DBA can go to look for information on how the server is performing. So many in fact that they can often overlap, which sometimes makes it hard to understand why tackling a new tool is worth the effort.

SQL Server is a huge product, with many different places a DBA can go to look for information on how the server is performing. So many in fact that they can often overlap, which sometimes makes it hard to understand why tackling a new tool is worth the effort.

Despite the fact that SQL Server Availability Groups are built on top of a stack of rather complex technology, over the years things have gotten to the point where getting an AG up and running for a simple two-node HA setup is not as intimidating for most DBAs as it may have been in the early days.

Most of us have heard that query hints should not be used very often in SQL Server. That said, how often do things actually break if we do use a few NOLOCK hints?

Despite the fact that SQL Server Availability Groups are built on top of a stack of rather complex technology, over the years things have gotten to the point where getting an AG up and running for a simple two-node HA setup is not as intimidating for most DBAs as it may have been in the early days.

Most of us have heard that query hints should not be used very often in SQL Server. That said, how often do things actually break if we do use a few NOLOCK hints?

After spending more than a decade completely devoted to the Microsoft stack, I did some time supporting a Java team. Yes, sure, Java is just another language so there aren't really and issues that are absolutely unique to the Java world.

SQL Server is a huge product, with many different places a DBA can go to look for information on how the server is performing. So many in fact that they can often overlap, which sometimes makes it hard to understand why tackling a new tool is worth the effort.

Amazon web services offers a befuddling number of of different services. Among these are the two major options for running SQL Server on AWS - Elastic Compute Cloud and Relational Database Services.