The Query Store
This week Steve Jones talks about the query store after an article was released describing it.
This week Steve Jones talks about the query store after an article was released describing it.
Performance tuning and optimization definitely have their place in minimizing SQL Server Licensing costs – by helping keep CPU utilization low. But it’s important to remember that the fastest and most efficient query possible is the one that you never execute against your SQL Server. That might sound trite, but it’s at the heart of caching – which is key to helping organizations save significant money on SQL Server licensing costs while simultaneously enabling better application performance and increased scalability.
This article describes a way to identify the user who truncated the table & how you can recover the data.
When SQL Server 2014 was released, it included Hekaton, Microsoft’s much talked about memory-optimized engine that brings In-Memory OLTP into play. With memory-optimized tables 30 times faster than disk-based tables, higher performance is promised – but at what cost? Jonathan Watts looks at the features that have improved, and those that need careful consideration.
In many occupations, workers invest in their own tools. However we rarely do that in technology.
Daniel Calbimonte has written a code comparison for MariaDB vs. SQL Server as it pertains to how to comment, how to create functions and procedures with parameters, how to store query results in a text file, how to show the top n rows in a query, how to use loops, and more.
Watch this short video on creating a striped backup for your database.
PlanTrace: Stop Reading Redshift EXPLAIN Plans. Start Seeing Them Introducing PlanTrace — a free, browser-based...
By Steve Jones
I went to sleep while reading a Kindle book on my phone. I know...
A conversation with Jan Laš, CIO at HOPI, about what deploying a data agent...
We suffered a SPAM attack from May 1-6, which unfortunately corresponded with time off...
Hi to all We have situation at a client where someone is illegally changing...
Hi to all We have situation at a client where someone is illegally changing...
I have this data in a table called dbo.NFLTeams
TeamID TeamName City YearEstablished ------ -------- ---- --------------- 1 Cowboys Dallas 1960 2 Eagles Philadelphia 1933 3 Packers Green Bay 1919 4 Chiefs Kansas City 1960 5 49ers San Francisco 1946 6 Broncos Denver 1960 7 Seahawks Seattle 1976 8 Patriots New England 1960If I run this code, how many rows are returned?
SELECT TOP 2
json_objectagg('Team' : TeamName)
FROM dbo.NFLTeams;
See possible answers