�ݺ�ߣshows by User: MarkusWinand

�ݺ�ߣshows by User: MarkusWinand / http://www.slideshare.net/images/logo.gif �ݺ�ߣshows by User: MarkusWinand / Sat, 03 Feb 2018 14:43:37 GMT �ݺ�ߣShare feed for �ݺ�ߣshows by User: MarkusWinand Standard SQL features where PostgreSQL beats its competitors /slideshow/standard-sql-features-where-postgresql-beats-its-competitors/87170097 postgresql-beats-180203144337
The SQL standard has more than 4300 pages and hundreds of optional features. The number of features offered by different products varies vastly. PostgreSQL implements a relativley large number of them. In this session I present some standard SQL features that work in PostgreSQL, but not in other popular open-source databases. But when it comes to standard conformance, PostgreSQL doesn’t even need to fear the comparison to its commercial competitors: PostgreSQL also supports a few useful standard SQL features that don’t work in any of the three most popular commercial SQL databases.]]>
The SQL standard has more than 4300 pages and hundreds of optional features. The number of features offered by different products varies vastly. PostgreSQL implements a relativley large number of them. In this session I present some standard SQL features that work in PostgreSQL, but not in other popular open-source databases. But when it comes to standard conformance, PostgreSQL doesn’t even need to fear the comparison to its commercial competitors: PostgreSQL also supports a few useful standard SQL features that don’t work in any of the three most popular commercial SQL databases.]]> Sat, 03 Feb 2018 14:43:37 GMT /slideshow/standard-sql-features-where-postgresql-beats-its-competitors/87170097 MarkusWinand@slideshare.net(MarkusWinand) Standard SQL features where PostgreSQL beats its competitors MarkusWinand The SQL standard has more than 4300 pages and hundreds of optional features. The number of features offered by different products varies vastly. PostgreSQL implements a relativley large number of them. In this session I present some standard SQL features that work in PostgreSQL, but not in other popular open-source databases. But when it comes to standard conformance, PostgreSQL doesn’t even need to fear the comparison to its commercial competitors: PostgreSQL also supports a few useful standard SQL features that don’t work in any of the three most popular commercial SQL databases. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/postgresql-beats-180203144337-thumbnail.jpg?width=120&height=120&fit=bounds" /> The SQL standard has more than 4300 pages and hundreds of optional features. The number of features offered by different products varies vastly. PostgreSQL implements a relativley large number of them. In this session I present some standard SQL features that work in PostgreSQL, but not in other popular open-source databases. But when it comes to standard conformance, PostgreSQL doesn’t even need to fear the comparison to its commercial competitors: PostgreSQL also supports a few useful standard SQL features that don’t work in any of the three most popular commercial SQL databases.

Standard SQL features where PostgreSQL beats its competitors from Markus Winand

]]> 59286 10 https://cdn.slidesharecdn.com/ss_thumbnails/postgresql-beats-180203144337-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Four* Major Database Releases of 2017 in Review /slideshow/four-major-database-releases-of-2017-in-review/86341395 fourreleases2017-180118095515
*Actually only three because MySQL 8.0 was not released GA in 2017.]]>
*Actually only three because MySQL 8.0 was not released GA in 2017.]]> Thu, 18 Jan 2018 09:55:15 GMT /slideshow/four-major-database-releases-of-2017-in-review/86341395 MarkusWinand@slideshare.net(MarkusWinand) Four* Major Database Releases of 2017 in Review MarkusWinand *Actually only three because MySQL 8.0 was not released GA in 2017. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/fourreleases2017-180118095515-thumbnail.jpg?width=120&height=120&fit=bounds" /> *Actually only three because MySQL 8.0 was not released GA in 2017.

Four* Major Database Releases of 2017 in Review from Markus Winand

]]> 1461 2 https://cdn.slidesharecdn.com/ss_thumbnails/fourreleases2017-180118095515-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Row Pattern Matching in SQL:2016 /slideshow/row-pattern-matching-in-sql2016/72932030 rowpatternmatching-170308072918
ISO SQL:2016 introduced Row Pattern Matching: a feature to apply (limited) regular expressions on table rows and perform analysis on each match. As of writing, this feature is only supported by the Oracle Database 12c.]]>
ISO SQL:2016 introduced Row Pattern Matching: a feature to apply (limited) regular expressions on table rows and perform analysis on each match. As of writing, this feature is only supported by the Oracle Database 12c.]]> Wed, 08 Mar 2017 07:29:18 GMT /slideshow/row-pattern-matching-in-sql2016/72932030 MarkusWinand@slideshare.net(MarkusWinand) Row Pattern Matching in SQL:2016 MarkusWinand ISO SQL:2016 introduced Row Pattern Matching: a feature to apply (limited) regular expressions on table rows and perform analysis on each match. As of writing, this feature is only supported by the Oracle Database 12c. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/rowpatternmatching-170308072918-thumbnail.jpg?width=120&height=120&fit=bounds" /> ISO SQL:2016 introduced Row Pattern Matching: a feature to apply (limited) regular expressions on table rows and perform analysis on each match. As of writing, this feature is only supported by the Oracle Database 12c.

Row Pattern Matching in SQL:2016 from Markus Winand

]]> 112333 13 https://cdn.slidesharecdn.com/ss_thumbnails/rowpatternmatching-170308072918-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 SQL Transactions - What they are good for and how they work /slideshow/sql-transactions-what-they-are-good-for-and-how-they-work/64488618 transactionsb-160728193256
This presentation focuses on how transactions affect read operations, how isolations levels work with locking and MVCC.]]>
This presentation focuses on how transactions affect read operations, how isolations levels work with locking and MVCC.]]> Thu, 28 Jul 2016 19:32:56 GMT /slideshow/sql-transactions-what-they-are-good-for-and-how-they-work/64488618 MarkusWinand@slideshare.net(MarkusWinand) SQL Transactions - What they are good for and how they work MarkusWinand This presentation focuses on how transactions affect read operations, how isolations levels work with locking and MVCC. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/transactionsb-160728193256-thumbnail.jpg?width=120&height=120&fit=bounds" /> This presentation focuses on how transactions affect read operations, how isolations levels work with locking and MVCC.

SQL Transactions - What they are good for and how they work from Markus Winand

]]> 34517 20 https://cdn.slidesharecdn.com/ss_thumbnails/transactionsb-160728193256-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Backend to Frontend: When database optimization affects the full stack /slideshow/backend-to-frontend-when-database-optimization-affects-the-full-stack/47045268 frontendtobackend-150415160100-conversion-gate01
OFFSET it the root of all evil: It's slow and actually delivers the wrong result. OFFSET is just not the right answer to implement pagination. There is a better approach, called Key-Set Pagination, that is superior in many regards. However, introducing it to your application affects the full technology stack up to "Layer 8": The User.]]>
OFFSET it the root of all evil: It's slow and actually delivers the wrong result. OFFSET is just not the right answer to implement pagination. There is a better approach, called Key-Set Pagination, that is superior in many regards. However, introducing it to your application affects the full technology stack up to "Layer 8": The User.]]> Wed, 15 Apr 2015 16:01:00 GMT /slideshow/backend-to-frontend-when-database-optimization-affects-the-full-stack/47045268 MarkusWinand@slideshare.net(MarkusWinand) Backend to Frontend: When database optimization affects the full stack MarkusWinand OFFSET it the root of all evil: It's slow and actually delivers the wrong result. OFFSET is just not the right answer to implement pagination. There is a better approach, called Key-Set Pagination, that is superior in many regards. However, introducing it to your application affects the full technology stack up to "Layer 8": The User. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/frontendtobackend-150415160100-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds" /> OFFSET it the root of all evil: It's slow and actually delivers the wrong result. OFFSET is just not the right answer to implement pagination. There is a better approach, called Key-Set Pagination, that is superior in many regards. However, introducing it to your application affects the full technology stack up to "Layer 8": The User.

Backend to Frontend: When database optimization affects the full stack from Markus Winand

]]> 3758 4 https://cdn.slidesharecdn.com/ss_thumbnails/frontendtobackend-150415160100-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Modern SQL in Open Source and Commercial Databases /slideshow/modern-sql/44086611 modernsqlinpostgresql-150130134147-conversion-gate01
SQL has gone out of fashion lately—partly due to the NoSQL movement, but mostly because SQL is often still used like 20 years ago. As a matter of fact, the SQL standard continued to evolve during the past decades resulting in the current release of 2016. In this session, we will go through the most important additions since the widely known SQL-92. We will cover common table expressions and window functions in detail and have a very short look at the temporal features of SQL:2011 and row pattern matching from SQL:2016. Links: http://modern-sql.com/ http://winand.at/ http://sql-performance-explained.com/]]>
SQL has gone out of fashion lately—partly due to the NoSQL movement, but mostly because SQL is often still used like 20 years ago. As a matter of fact, the SQL standard continued to evolve during the past decades resulting in the current release of 2016. In this session, we will go through the most important additions since the widely known SQL-92. We will cover common table expressions and window functions in detail and have a very short look at the temporal features of SQL:2011 and row pattern matching from SQL:2016. Links: http://modern-sql.com/ http://winand.at/ http://sql-performance-explained.com/]]> Fri, 30 Jan 2015 13:41:47 GMT /slideshow/modern-sql/44086611 MarkusWinand@slideshare.net(MarkusWinand) Modern SQL in Open Source and Commercial Databases MarkusWinand SQL has gone out of fashion lately—partly due to the NoSQL movement, but mostly because SQL is often still used like 20 years ago. As a matter of fact, the SQL standard continued to evolve during the past decades resulting in the current release of 2016. In this session, we will go through the most important additions since the widely known SQL-92. We will cover common table expressions and window functions in detail and have a very short look at the temporal features of SQL:2011 and row pattern matching from SQL:2016. Links: http://modern-sql.com/ http://winand.at/ http://sql-performance-explained.com/ <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/modernsqlinpostgresql-150130134147-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds" /> SQL has gone out of fashion lately—partly due to the NoSQL movement, but mostly because SQL is often still used like 20 years ago. As a matter of fact, the SQL standard continued to evolve during the past decades resulting in the current release of 2016. In this session, we will go through the most important additions since the widely known SQL-92. We will cover common table expressions and window functions in detail and have a very short look at the temporal features of SQL:2011 and row pattern matching from SQL:2016. Links: http://modern-sql.com/ http://winand.at/ http://sql-performance-explained.com/

Modern SQL in Open Source and Commercial Databases from Markus Winand

]]> 452710 58 https://cdn.slidesharecdn.com/ss_thumbnails/modernsqlinpostgresql-150130134147-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Volkskrankheit "Stiefmuetterliche Indizierung" https://de.slideshare.net/slideshow/volkskrankheit-stiefmuetterliche-indizierung/30009102 volkskrankheitstiefmuetterlicheindizierung-140114120929-phpapp01
]]>
]]> Tue, 14 Jan 2014 12:09:29 GMT https://de.slideshare.net/slideshow/volkskrankheit-stiefmuetterliche-indizierung/30009102 MarkusWinand@slideshare.net(MarkusWinand) Volkskrankheit "Stiefmuetterliche Indizierung" MarkusWinand <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/volkskrankheitstiefmuetterlicheindizierung-140114120929-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" />

from Markus Winand

]]> 16368 49 https://cdn.slidesharecdn.com/ss_thumbnails/volkskrankheitstiefmuetterlicheindizierung-140114120929-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 SQL Performance - Vienna System Architects Meetup 20131202 /slideshow/vienna-system-architects-meetup-20131202/28831027 viennasystemarchitectsmeetup20131202-131203002315-phpapp02
]]>
]]> Tue, 03 Dec 2013 00:23:15 GMT /slideshow/vienna-system-architects-meetup-20131202/28831027 MarkusWinand@slideshare.net(MarkusWinand) SQL Performance - Vienna System Architects Meetup 20131202 MarkusWinand <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/viennasystemarchitectsmeetup20131202-131203002315-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" />

SQL Performance - Vienna System Architects Meetup 20131202 from Markus Winand

]]> 1843 3 https://cdn.slidesharecdn.com/ss_thumbnails/viennasystemarchitectsmeetup20131202-131203002315-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Indexes: The neglected performance all rounder /slideshow/indexes-neglectedperformanceallrounder/24103160 indexes-neglected-performance-all-rounder-130710103108-phpapp01
The latest incarnation of this talk as presented on Jan, 31st at FOSDEM PgDay in Brussles]]>
The latest incarnation of this talk as presented on Jan, 31st at FOSDEM PgDay in Brussles]]> Wed, 10 Jul 2013 10:31:08 GMT /slideshow/indexes-neglectedperformanceallrounder/24103160 MarkusWinand@slideshare.net(MarkusWinand) Indexes: The neglected performance all rounder MarkusWinand The latest incarnation of this talk as presented on Jan, 31st at FOSDEM PgDay in Brussles <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/indexes-neglected-performance-all-rounder-130710103108-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> The latest incarnation of this talk as presented on Jan, 31st at FOSDEM PgDay in Brussles

Indexes: The neglected performance all rounder from Markus Winand

]]> 35777 9 https://cdn.slidesharecdn.com/ss_thumbnails/indexes-neglected-performance-all-rounder-130710103108-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Pagination Done the Right Way /slideshow/p2d2-pagination-done-the-postgresql-way/22210863 paginationdonethepostgresqlwayv2-130530141009-phpapp02
The SQL OFFSET keyword is evil. It basically behaves like SLEEP in other programming langauges: the bigger the number, the slower the execution. Fetching results in a page-by-page fashion in SQL doesn't require OFFSET at all but an even simpler SQL clause. Besides being faster, you don't have to cope with drifting results if new data is inserted between two page fetches.]]>
The SQL OFFSET keyword is evil. It basically behaves like SLEEP in other programming langauges: the bigger the number, the slower the execution. Fetching results in a page-by-page fashion in SQL doesn't require OFFSET at all but an even simpler SQL clause. Besides being faster, you don't have to cope with drifting results if new data is inserted between two page fetches.]]> Thu, 30 May 2013 14:10:09 GMT /slideshow/p2d2-pagination-done-the-postgresql-way/22210863 MarkusWinand@slideshare.net(MarkusWinand) Pagination Done the Right Way MarkusWinand The SQL OFFSET keyword is evil. It basically behaves like SLEEP in other programming langauges: the bigger the number, the slower the execution. Fetching results in a page-by-page fashion in SQL doesn't require OFFSET at all but an even simpler SQL clause. Besides being faster, you don't have to cope with drifting results if new data is inserted between two page fetches. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/paginationdonethepostgresqlwayv2-130530141009-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> The SQL OFFSET keyword is evil. It basically behaves like SLEEP in other programming langauges: the bigger the number, the slower the execution. Fetching results in a page-by-page fashion in SQL doesn't require OFFSET at all but an even simpler SQL clause. Besides being faster, you don't have to cope with drifting results if new data is inserted between two page fetches.

Pagination Done the Right Way from Markus Winand

]]> 442364 24 https://cdn.slidesharecdn.com/ss_thumbnails/paginationdonethepostgresqlwayv2-130530141009-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 https://cdn.slidesharecdn.com/profile-photo-MarkusWinand-48x48.jpg?cb=1536919757 http://winand.at/ https://cdn.slidesharecdn.com/ss_thumbnails/postgresql-beats-180203144337-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/standard-sql-features-where-postgresql-beats-its-competitors/87170097 Standard SQL features ... https://cdn.slidesharecdn.com/ss_thumbnails/fourreleases2017-180118095515-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/four-major-database-releases-of-2017-in-review/86341395 Four* Major Database R... https://cdn.slidesharecdn.com/ss_thumbnails/rowpatternmatching-170308072918-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/row-pattern-matching-in-sql2016/72932030 Row Pattern Matching i...