Heaps in SQL Server: Part 3 Nonclustered Indexes
Uwe Ricken continues his series on heaps. This time he demonstrates a common scenario where the query against a heap is faster than a clustered index.
2020-09-17
Additional Articles
Power BI Histogram Example using DAX
Companies use a Bell Curve approach to measure performance. As part of this approach they create a histogram. A histogram is a statistical concept and according to Wikipedia it is defined as a graphical distribution of the numerical data. A histogram is made of several bins and bins can be considered a range of values or a benchmark
2020-09-16
When SQL Server Performance Goes Bad: Rogue Indexes
Phil Factor explains how SQL Monitor helps focus performance tuning efforts on the tables and queries where 'rogue indexes' might be a significant problem, and then how to identify both 'missing' indexes that might be beneficial to the overall workload, and those that are unused or duplicated, and so are doing more harm than good.
2020-09-16
SQL Server Wait Stats Monitoring with PowerShell
In this article we add another module to the PowerShell monitoring process to capture wait stats for all monitored SQL Server instances.
2020-09-15
Fully Left-Shifted Deployments with Version Control and Automatic Cloning
Discover the future of DevOps! Join Microsoft MVP Kendra Little to see Redgate's recent innovations in action and give you a picture of where Database DevOps is going, and why.
2020-09-14
Storage 101: The Future of Storage
Robert Sheldon wraps up his series on storage by discussing the latest storage innovation and ideas.
2020-09-14
Delete Duplicate Rows with No Primary Key on a SQL Server Table
Every once in awhile a table gets created without a primary key and duplicate records get entered. The problem gets even worse when you have two identical rows in the table and there is no way to distinguish between the two rows. So how do you delete the duplicate record?
2020-09-11
When SQL Server Performance Goes Bad: Implicit Conversions
When you're developing a database, the pressure is on to get something that works, using an efficient algorithm. When you are getting close to a release candidate, however, there are some programming habits that must be removed from the code, because they can cause unexpected performance problems. In this article, you'll learn how to detect and remove one such problem: reliance on implicit datatype conversions in your queries. We'll use a combination of plan cache queries, extended events, and SQL Monitor.
2020-09-11
The Two Ways Containers Will Revolutionize Database DevOps
Containers have already transformed the way application development works, but adoption has been slower for databases. Finally, the revolution is beginning. In this post, Kendra Little shares the two ways in which containers will dramatically change the way teams develop and deploy database changes.
2020-09-10
Half Of You Don’t Understand Variables and Transactions.
Do table variables and variables respect transactions? If we set the value of a variable during a transaction, and we roll it back, what happens?
2020-09-09
Blogs
Blog a Day – Day 1: History of AI
By Vinay Thakur
it has been a year since i have not written much on the blog...
A New Word: on tenderhooks
By Steve Jones
on tenderhooks – adj. feeling the primal satisfaction of being needed by someone, which...
Ramblings about data communities and your contributions, no excuses
By DataOnWheels
I have been active in the data community throughout my career. I have met...
Forums
A Quick Restore
Comments posted to this topic are about the item A Quick Restore
Guarding Against SQL Injection at the Database Layer (SQL Server)
Comments posted to this topic are about the item Guarding Against SQL Injection at...
Ola Hallengren Index Optimize Maintenance can we have data compression = page
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
Question of the Day
A Quick Restore
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers