Receive SQL Server Alerts through Slack
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
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,270 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,670 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,362 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,686 reads
In Windows Server 2016, Microsoft have implemented a strong security concept called Shielded Virtual Machines. Shielded VMs have been improved in the Windows Server 2019 release. In the second part of this series, Nicolas describes what Shielded Virtual Machines are and how to configure them using PowerShell.
2018-06-18
2,979 reads
By gbargsley
It's 2 AM. Your phone is going off. Users can't connect to the application,...
By Steve Jones
I discovered a procedure recently that I wasn’t aware of: sp_sequence_get_range. This post looks...
By Arun Sirpal
After a year away getting to grips with AI and its application across the...
Fisher Phillips is looking for a Financial Systems Administrator to help support and improve our financial...
Employee owned company, been around for over 50 years. Hybrid opportunity, looking folks in Pacific...
i have huge table with lot of data and is also wide. i took...
I want to create a JSON document that contains data from this table:
TeamID TeamNameCity YearEstablished 1 Cowboys Dallas 1960 2 Eagles Philadelphia 1933 3 Packers Green Bay 1919 4 Chiefs Kansas City 1960If I run this code, what document(s) is/are returned?
SELECT json_objectagg( n.city : n.TeamName) FROM dbo.NFLTeams;See possible answers