Power BI Desktop is the free tool from Microsoft for developing in Power BI. In this article, Robert Sheldon walks you through importing and manipulating data with the Query Editor in Power BI Desktop.
2018-06-25
3,270 reads
In this tip we look at how we can use Python and SQL Server 2017 to send alerts from SQL Server to Slack messaging service.
2018-06-25
2,903 reads
How to create an automatic SQL restart or failover notification.
2018-06-22 (first published: 2015-12-10)
10,228 reads
Stuffing table variables with hard-coded values to demonstrate concurrency.
2018-06-22
2,793 reads
In-Memory OLTP is a high performance, memory-optimized engine integrated into SQL Server 2014 and designed for modern hardware trends. In-Memory OLTP allows users to move data into memory resident tables while keeping other data in traditional, disk-based table structures. For performance critical workloads, users can also migrate Transact-SQL code to natively compiled stored procedures. This can provide additional performance gains. This paper aims to help readers understand some of the common architectural patterns where In-Memory OLTP has provided significant benefits. The paper also discusses considerations for migrating applications to In-Memory OLTP.
2018-06-22
2,677 reads
A walkthrough of a conversion of a SQL Trace setup to an Extended Event session.
2018-06-21
1,666 reads
In-Memory OLTP (project “Hekaton”) is a new database engine component, fully integrated into SQL Server. It is optimized for OLTP workloads accessing memory resident data. In-Memory OLTP allows OLTP workloads to achieve significant improvements in performance, and reduction in processing time. Tables can be declared as ‘memory optimized’ to enable In-Memory OLTP’s capabilities. Memory-optimized tables are fully transactional and can be accessed using Transact-SQL. Transact-SQL stored procedures can be compiled to machine code for further performance improvements on memory-optimized tables. The engine is designed for high concurrency and blocking is minimal.
2018-06-21
2,997 reads
2018-06-19
8,344 reads
Every DBA needs to appropriately manage database growth. No DBA wants an application to fail because the database is out of space. A database can run out of space a number of different ways. One of those ways is to set the MAXSIZE of a database. When the database grows to the MAXSIZE the database will not grow anymore and if someone tries to add more rows they will get an error saying the database is full.
2018-06-19
2,410 reads
Will there be a fair balance between the coming generations of technology and the human workforce? Here is a list of industries that may not think yes.
2018-06-18
1,680 reads
By James Serra
Organizations increasingly want Snowflake and Microsoft Fabric to coexist without duplicating data or fragmenting...
By Steve Jones
In a previous post, I deployed a model to a database using SQL Compare...
By SQLPals
Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022 ...
Comments posted to this topic are about the item Automating Database Cleanup for PostgreSQL...
Comments posted to this topic are about the item The Query Optimizer and Page...
Comments posted to this topic are about the item There Are a Lot of...
If I have a fillfactor set to 70%, this reduces my page density to roughly 70%. Does this affect the query plans that the optimizer chooses?
See possible answers