#dba — Public Fediverse posts

Grow your #PostgreSQL, #opensource skills and grab a 20% discount on LPI exams at @pgdata2026, June 4–5 in Chicago.

Linux Professional Institute (LPI) is a Community Partner for this new #Postgres conference series exploring education, community-building, and academic outreach.

Learn more 🔗 https://lpi.org/sysr

See you there! 🐧👋

@prairie_postgres #LPI #pgdata #pgdata2026 #postgresql #opensource #linux #FOSS #prairiepostgres #postgres #performance #dba #sql #database #developers

PSBlitz 6.1.0 is live
New checks for Backups (RPO/RPO est.) & Instance Security (beta).
ImportExcel support
Up to 70% faster Excel exports
Retry logic for transient errors

Read the full breakdown: https://vladdba.com/2026/05/28/psblitz-6-1-0-backup-security-checks-excel-performance/
Repo: https://github.com/VladDBA/PSBlitz

#sqlserver #sqldba #powershell #microsoftsqlserver #mssqlserver #mssql #mssqldba #dba #PSBlitz #MVPBuzz

PSBlitz 6.1.0 is live
New checks for Backups (RPO/RPO est.) & Instance Security (beta).
ImportExcel support
Up to 70% faster Excel exports
Retry logic for transient errors

Read the full breakdown: https://vladdba.com/2026/05/28/psblitz-6-1-0-backup-security-checks-excel-performance/
Repo: https://github.com/VladDBA/PSBlitz

#sqlserver #sqldba #powershell #microsoftsqlserver #mssqlserver #mssql #mssqldba #dba #PSBlitz #MVPBuzz

PSBlitz 6.1.0 is live
New checks for Backups (RPO/RPO est.) & Instance Security (beta).
ImportExcel support
Up to 70% faster Excel exports
Retry logic for transient errors

Read the full breakdown: https://vladdba.com/2026/05/28/psblitz-6-1-0-backup-security-checks-excel-performance/
Repo: https://github.com/VladDBA/PSBlitz

#sqlserver #sqldba #powershell #microsoftsqlserver #mssqlserver #mssql #mssqldba #dba #PSBlitz #MVPBuzz

Not many databases have a keynote from the person who invented them.

#PgDayBoston is June 9 at the Museum of Science - a one-day community conference organized by #PostgreSQL US - and Michael Stonebraker is keynoting. MIT adjunct professor, 2014 ACM Turing Award winner, primary inventor of #Postgres. He's going to walk through his journey building it. 🐘

📅 June 9, 2026
📍 Museum of Science in Boston
🎟️ https://2026.pgdayboston.org/registration/

#database #dba #conference #opensource #boston #dataengineering

Not many databases have a keynote from the person who invented them.

#PgDayBoston is June 9 at the Museum of Science - a one-day community conference organized by #PostgreSQL US - and Michael Stonebraker is keynoting. MIT adjunct professor, 2014 ACM Turing Award winner, primary inventor of #Postgres. He's going to walk through his journey building it. 🐘

📅 June 9, 2026
📍 Museum of Science in Boston
🎟️ https://2026.pgdayboston.org/registration/

#database #dba #conference #opensource #boston #dataengineering

Not many databases have a keynote from the person who invented them.

#PgDayBoston is June 9 at the Museum of Science - a one-day community conference organized by #PostgreSQL US - and Michael Stonebraker is keynoting. MIT adjunct professor, 2014 ACM Turing Award winner, primary inventor of #Postgres. He's going to walk through his journey building it. 🐘

📅 June 9, 2026
📍 Museum of Science in Boston
🎟️ https://2026.pgdayboston.org/registration/

#database #dba #conference #opensource #boston #dataengineering

Not many databases have a keynote from the person who invented them.

#PgDayBoston is June 9 at the Museum of Science - a one-day community conference organized by #PostgreSQL US - and Michael Stonebraker is keynoting. MIT adjunct professor, 2014 ACM Turing Award winner, primary inventor of #Postgres. He's going to walk through his journey building it. 🐘

📅 June 9, 2026
📍 Museum of Science in Boston
🎟️ https://2026.pgdayboston.org/registration/

#database #dba #conference #opensource #boston #dataengineering

It's been said that experience is a comb life gives you after your hair has fallen out.

#SQLServer
#SQL
#Development
#DBA

It's been said that experience is a comb life gives you after your hair has fallen out.

#SQLServer
#SQL
#Development
#DBA

It's been said that experience is a comb life gives you after your hair has fallen out.

#SQLServer
#SQL
#Development
#DBA

It's been said that experience is a comb life gives you after your hair has fallen out.

#SQLServer
#SQL
#Development
#DBA

It's been said that experience is a comb life gives you after your hair has fallen out.

#SQLServer
#SQL
#Development
#DBA

explain prettier from Andrei Lepikhov strips platform-dependent noise from EXPLAIN output, keeps plan structure intact. Two functions, no deps.

pretty_explain_analyze() runs and cleans.

pretty_explain_text() filters existing output, useful without server access.

Check out the code: ⭐ https://github.com/danolivo/conf/blob/main/2026b-explain-prettier/explain-prettier.sql

Read the full write-up: 📖 https://www.pgedge.com/blog/explain-prettier-or-post-processing-query-plans-in-postgres

#postgresql #dba #testing #devtools #regression

explain prettier from Andrei Lepikhov strips platform-dependent noise from EXPLAIN output, keeps plan structure intact. Two functions, no deps.

pretty_explain_analyze() runs and cleans.

pretty_explain_text() filters existing output, useful without server access.

Check out the code: ⭐ https://github.com/danolivo/conf/blob/main/2026b-explain-prettier/explain-prettier.sql

Read the full write-up: 📖 https://www.pgedge.com/blog/explain-prettier-or-post-processing-query-plans-in-postgres

#postgresql #dba #testing #devtools #regression

explain prettier from Andrei Lepikhov strips platform-dependent noise from EXPLAIN output, keeps plan structure intact. Two functions, no deps.

pretty_explain_analyze() runs and cleans.

pretty_explain_text() filters existing output, useful without server access.

Check out the code: ⭐ https://github.com/danolivo/conf/blob/main/2026b-explain-prettier/explain-prettier.sql

Read the full write-up: 📖 https://www.pgedge.com/blog/explain-prettier-or-post-processing-query-plans-in-postgres

#postgresql #dba #testing #devtools #regression

explain prettier from Andrei Lepikhov strips platform-dependent noise from EXPLAIN output, keeps plan structure intact. Two functions, no deps.

pretty_explain_analyze() runs and cleans.

pretty_explain_text() filters existing output, useful without server access.

Check out the code: ⭐ https://github.com/danolivo/conf/blob/main/2026b-explain-prettier/explain-prettier.sql

Read the full write-up: 📖 https://www.pgedge.com/blog/explain-prettier-or-post-processing-query-plans-in-postgres

#postgresql #dba #testing #devtools #regression

Another reason: object types sometimes change. For years my organization had a table named dbo.tbl_FooBar.

To overcome performance problems involved with populating & syncing the table, it was replaced with a VIEW. The old table was referenced in too many places to warrant changing the object name. So we didn't.

And now we have a VIEW named dbo.tbl_FooBar. And that's just messed up.

#SQLServer
#Databases
#DBA

Another reason: object types sometimes change. For years my organization had a table named dbo.tbl_FooBar.

To overcome performance problems involved with populating & syncing the table, it was replaced with a VIEW. The old table was referenced in too many places to warrant changing the object name. So we didn't.

And now we have a VIEW named dbo.tbl_FooBar. And that's just messed up.

#SQLServer
#Databases
#DBA

Another reason: object types sometimes change. For years my organization had a table named dbo.tbl_FooBar.

To overcome performance problems involved with populating & syncing the table, it was replaced with a VIEW. The old table was referenced in too many places to warrant changing the object name. So we didn't.

And now we have a VIEW named dbo.tbl_FooBar. And that's just messed up.

#SQLServer
#Databases
#DBA

Another reason: object types sometimes change. For years my organization had a table named dbo.tbl_FooBar.

To overcome performance problems involved with populating & syncing the table, it was replaced with a VIEW. The old table was referenced in too many places to warrant changing the object name. So we didn't.

And now we have a VIEW named dbo.tbl_FooBar. And that's just messed up.

#SQLServer
#Databases
#DBA

Another reason: object types sometimes change. For years my organization had a table named dbo.tbl_FooBar.

To overcome performance problems involved with populating & syncing the table, it was replaced with a VIEW. The old table was referenced in too many places to warrant changing the object name. So we didn't.

And now we have a VIEW named dbo.tbl_FooBar. And that's just messed up.

#SQLServer
#Databases
#DBA

Why?

For probably 20 years or so, development tools (like SQL Server Management Studio and Visual Studio) have been sophisticated enough to indicate an object's type via tool tips (they usually pop up when you hover the mouse cursor/icon over the object's name).

You can see an SSMS example in the attached picture. Microsoft didn't use Hungarian notation, and it's not necessary--we clearly see the object is a VIEW.

#SQLServer
#Databases
#DBA

Why?

For probably 20 years or so, development tools (like SQL Server Management Studio and Visual Studio) have been sophisticated enough to indicate an object's type via tool tips (they usually pop up when you hover the mouse cursor/icon over the object's name).

You can see an SSMS example in the attached picture. Microsoft didn't use Hungarian notation, and it's not necessary--we clearly see the object is a VIEW.

#SQLServer
#Databases
#DBA

Why?

For probably 20 years or so, development tools (like SQL Server Management Studio and Visual Studio) have been sophisticated enough to indicate an object's type via tool tips (they usually pop up when you hover the mouse cursor/icon over the object's name).

You can see an SSMS example in the attached picture. Microsoft didn't use Hungarian notation, and it's not necessary--we clearly see the object is a VIEW.

#SQLServer
#Databases
#DBA

Why?

For probably 20 years or so, development tools (like SQL Server Management Studio and Visual Studio) have been sophisticated enough to indicate an object's type via tool tips (they usually pop up when you hover the mouse cursor/icon over the object's name).

You can see an SSMS example in the attached picture. Microsoft didn't use Hungarian notation, and it's not necessary--we clearly see the object is a VIEW.

#SQLServer
#Databases
#DBA

Why?

For probably 20 years or so, development tools (like SQL Server Management Studio and Visual Studio) have been sophisticated enough to indicate an object's type via tool tips (they usually pop up when you hover the mouse cursor/icon over the object's name).

You can see an SSMS example in the attached picture. Microsoft didn't use Hungarian notation, and it's not necessary--we clearly see the object is a VIEW.

#SQLServer
#Databases
#DBA

As the saying in IT goes, "Naming things is hard". Coming up with a naming convention everyone agrees on is even more difficult.

For SQL Server database objects, one 'rule' I try to always follow is to *not* use Hungarian notation, which involves prefixing an object name to indicate the object type. For example a "tbl_" prefix for tables or "vw_" for views.

#SQLServer
#Databases
#DBA

As the saying in IT goes, "Naming things is hard". Coming up with a naming convention everyone agrees on is even more difficult.

For SQL Server database objects, one 'rule' I try to always follow is to *not* use Hungarian notation, which involves prefixing an object name to indicate the object type. For example a "tbl_" prefix for tables or "vw_" for views.

#SQLServer
#Databases
#DBA

As the saying in IT goes, "Naming things is hard". Coming up with a naming convention everyone agrees on is even more difficult.

For SQL Server database objects, one 'rule' I try to always follow is to *not* use Hungarian notation, which involves prefixing an object name to indicate the object type. For example a "tbl_" prefix for tables or "vw_" for views.

#SQLServer
#Databases
#DBA

As the saying in IT goes, "Naming things is hard". Coming up with a naming convention everyone agrees on is even more difficult.

For SQL Server database objects, one 'rule' I try to always follow is to *not* use Hungarian notation, which involves prefixing an object name to indicate the object type. For example a "tbl_" prefix for tables or "vw_" for views.

#SQLServer
#Databases
#DBA

As the saying in IT goes, "Naming things is hard". Coming up with a naming convention everyone agrees on is even more difficult.

For SQL Server database objects, one 'rule' I try to always follow is to *not* use Hungarian notation, which involves prefixing an object name to indicate the object type. For example a "tbl_" prefix for tables or "vw_" for views.

#SQLServer
#Databases
#DBA

Attend @pgdata2026, a new PostgreSQL conference series featuring educational sessions, operational guidance, #opensource exploration, and more, June 4–5 in Chicago!

LPI joins the event as a proud Community Partner. Visit us to get a 20% discount on our exams and validate your #Linux and #FOSS skills with globally recognized credentials! 🐧

Learn more: https://lpi.org/sysr

@prairie_postgres #LPI #pgdata #pgdata2026 #postgresql #opensource #linux #FOSS #prairiepostgres #postgres #dba

Attend @pgdata2026, a new PostgreSQL conference series featuring educational sessions, operational guidance, #opensource exploration, and more, June 4–5 in Chicago!

LPI joins the event as a proud Community Partner. Visit us to get a 20% discount on our exams and validate your #Linux and #FOSS skills with globally recognized credentials! 🐧

Learn more: https://lpi.org/sysr

@prairie_postgres #LPI #pgdata #pgdata2026 #postgresql #opensource #linux #FOSS #prairiepostgres #postgres #dba

Attend @pgdata2026, a new PostgreSQL conference series featuring educational sessions, operational guidance, #opensource exploration, and more, June 4–5 in Chicago!

LPI joins the event as a proud Community Partner. Visit us to get a 20% discount on our exams and validate your #Linux and #FOSS skills with globally recognized credentials! 🐧

Learn more: https://lpi.org/sysr

@prairie_postgres #LPI #pgdata #pgdata2026 #postgresql #opensource #linux #FOSS #prairiepostgres #postgres #dba

Attend @pgdata2026, a new PostgreSQL conference series featuring educational sessions, operational guidance, #opensource exploration, and more, June 4–5 in Chicago!

LPI joins the event as a proud Community Partner. Visit us to get a 20% discount on our exams and validate your #Linux and #FOSS skills with globally recognized credentials! 🐧

Learn more: https://lpi.org/sysr

@prairie_postgres #LPI #pgdata #pgdata2026 #postgresql #opensource #linux #FOSS #prairiepostgres #postgres #dba

Attend @pgdata2026, a new PostgreSQL conference series featuring educational sessions, operational guidance, #opensource exploration, and more, June 4–5 in Chicago!

LPI joins the event as a proud Community Partner. Visit us to get a 20% discount on our exams and validate your #Linux and #FOSS skills with globally recognized credentials! 🐧

Learn more: https://lpi.org/sysr

@prairie_postgres #LPI #pgdata #pgdata2026 #postgresql #opensource #linux #FOSS #prairiepostgres #postgres #dba

Spannende Talks, starke Community und jede Menge PostgreSQL-Insights beim Nordic PGDay 2026 in Helsinki 🇫🇮

Unser Vortrag „Beyond work_mem Myths“ zeigte, warum PostgreSQL Memory Usage oft unterschätzt wird und weshalb work_mem kein hartes Limit ist.

Danke an alle Beteiligten für ein großartiges Event – wir freuen uns schon aufs nächste Jahr! 🚀

Mehr dazu: https://www.credativ.de/blog/postgresql/nordic-pgday-2026-im-gluecklichsten-land-der-welt/

#PostgreSQL #Postgres #PGDay #NordicPGDay #OpenSource #Database #DBA #Helsinki #TechConference #DevOps #credativ

Spannende Talks, starke Community und jede Menge PostgreSQL-Insights beim Nordic PGDay 2026 in Helsinki 🇫🇮

Unser Vortrag „Beyond work_mem Myths“ zeigte, warum PostgreSQL Memory Usage oft unterschätzt wird und weshalb work_mem kein hartes Limit ist.

Danke an alle Beteiligten für ein großartiges Event – wir freuen uns schon aufs nächste Jahr! 🚀

Mehr dazu: https://www.credativ.de/blog/postgresql/nordic-pgday-2026-im-gluecklichsten-land-der-welt/

#PostgreSQL #Postgres #PGDay #NordicPGDay #OpenSource #Database #DBA #Helsinki #TechConference #DevOps #credativ

Spannende Talks, starke Community und jede Menge PostgreSQL-Insights beim Nordic PGDay 2026 in Helsinki 🇫🇮

Unser Vortrag „Beyond work_mem Myths“ zeigte, warum PostgreSQL Memory Usage oft unterschätzt wird und weshalb work_mem kein hartes Limit ist.

Danke an alle Beteiligten für ein großartiges Event – wir freuen uns schon aufs nächste Jahr! 🚀

Mehr dazu: https://www.credativ.de/blog/postgresql/nordic-pgday-2026-im-gluecklichsten-land-der-welt/

#PostgreSQL #Postgres #PGDay #NordicPGDay #OpenSource #Database #DBA #Helsinki #TechConference #DevOps #credativ

Spannende Talks, starke Community und jede Menge PostgreSQL-Insights beim Nordic PGDay 2026 in Helsinki 🇫🇮

Unser Vortrag „Beyond work_mem Myths“ zeigte, warum PostgreSQL Memory Usage oft unterschätzt wird und weshalb work_mem kein hartes Limit ist.

Danke an alle Beteiligten für ein großartiges Event – wir freuen uns schon aufs nächste Jahr! 🚀

Mehr dazu: https://www.credativ.de/blog/postgresql/nordic-pgday-2026-im-gluecklichsten-land-der-welt/

#PostgreSQL #Postgres #PGDay #NordicPGDay #OpenSource #Database #DBA #Helsinki #TechConference #DevOps #credativ

Spannende Talks, starke Community und jede Menge PostgreSQL-Insights beim Nordic PGDay 2026 in Helsinki 🇫🇮

Unser Vortrag „Beyond work_mem Myths“ zeigte, warum PostgreSQL Memory Usage oft unterschätzt wird und weshalb work_mem kein hartes Limit ist.

Danke an alle Beteiligten für ein großartiges Event – wir freuen uns schon aufs nächste Jahr! 🚀

Mehr dazu: https://www.credativ.de/blog/postgresql/nordic-pgday-2026-im-gluecklichsten-land-der-welt/

#PostgreSQL #Postgres #PGDay #NordicPGDay #OpenSource #Database #DBA #Helsinki #TechConference #DevOps #credativ

RELEASE : annonce de fin de vie de la v.14, correctifs de sécurité, améliorations et conseils pour mettre à jour votre #SGBD… Voici notre traduction de l'annonce communautaire =>
https://dali.bo/202605_release_mineure

#PostgreSQL #opensource #DBA #update

RELEASE : annonce de fin de vie de la v.14, correctifs de sécurité, améliorations et conseils pour mettre à jour votre #SGBD… Voici notre traduction de l'annonce communautaire =>
https://dali.bo/202605_release_mineure

#PostgreSQL #opensource #DBA #update

RELEASE : annonce de fin de vie de la v.14, correctifs de sécurité, améliorations et conseils pour mettre à jour votre #SGBD… Voici notre traduction de l'annonce communautaire =>
https://dali.bo/202605_release_mineure

#PostgreSQL #opensource #DBA #update

RELEASE : annonce de fin de vie de la v.14, correctifs de sécurité, améliorations et conseils pour mettre à jour votre #SGBD… Voici notre traduction de l'annonce communautaire =>
https://dali.bo/202605_release_mineure

#PostgreSQL #opensource #DBA #update

RELEASE : annonce de fin de vie de la v.14, correctifs de sécurité, améliorations et conseils pour mettre à jour votre #SGBD… Voici notre traduction de l'annonce communautaire =>
https://dali.bo/202605_release_mineure

#PostgreSQL #opensource #DBA #update

RE: https://mastodon.online/@dalibo/116436423759084762

Conférence en ligne ici : https://www.youtube.com/watch?v=fefje1HXW48&list=PLdz5EN2NV_7CwT7CuuOjdv6KXkG2r5GGO&index=1

Merci aux organisateurs du Devoxx France pour le partage !

#PostgreSQL #SGBD #DBA
#observabilité

RE: https://mastodon.online/@dalibo/116436423759084762

Conférence en ligne ici : https://www.youtube.com/watch?v=fefje1HXW48&list=PLdz5EN2NV_7CwT7CuuOjdv6KXkG2r5GGO&index=1

Merci aux organisateurs du Devoxx France pour le partage !

#PostgreSQL #SGBD #DBA
#observabilité

RE: https://mastodon.online/@dalibo/116436423759084762

Conférence en ligne ici : https://www.youtube.com/watch?v=fefje1HXW48&list=PLdz5EN2NV_7CwT7CuuOjdv6KXkG2r5GGO&index=1

Merci aux organisateurs du Devoxx France pour le partage !

#PostgreSQL #SGBD #DBA
#observabilité