Ten Commandments when you install SQL server

  1. Above all, Install SQL server with much fun and devotion.
  2. Preconfigure TEMPDB, not leaving defaults, for better throughput and performance.
  3. You shall protect the data and make back-ups as if it was the Chosen one.
  4. Test, Test and Test the restoring of data in order to anticipate on future disasters, this might be your salvation.
  5. Thou shallt install SQL server updates and patches after testing.
  6. Carve traceflags into stone, they can relieve the pressure and pain.
  7. Spend time setting up appropriate maintenance as if it were fitness to your body. It will keep your database healthy after you install SQL server.
  8. Make adjustments to default growth. Let databases grow by chunks wisely chosen in megabytes.
  9. Tailor your degree of parallellism and Cost treshold for parallellism.
  10. As an addendum, consider using volume maintenance tasks, lock pages in memory.
Your Modernization Journey starts now
Recently Microsoft introduced SQL server 2022. We wrote this post to make sure you won’t be missing out on all the fun and exciting new...
Parameter sniffing solved with new Parameter Sensitive Plan Optimization feature
If you’re someone that works a lot with Microsoft SQL Server, there’s no doubt that you’ve had issues with an issue called “Parameter sniffing” before....
Creating maps with R and Power BI
The possibilities are infinite when it comes to creating custom visuals in Power BI. As long as you are creative and have knowledge about the...
Reading monitoring alerts in Telegram
Sending monitoring alerts through Telegram
What if you could get the ease of phone notifications for whatever monitoring alerts you need? Then we have a solution for you with the...
Send mails with Azure Elastic Database Jobs
The DatabaseMail feature in SQL Server and Managed Instance is widely used by many professionals. But what if you want similar functionality in Azure SQL...
Sorting matrices in Power BI
Recently I worked on a Power BI project for a client. They had a SharePoint site where they regularly published articles and wanted to pour...