2020-07-03
536 reads
heap
Identify and Correct SQL Server Forwarded Records
Forwarded records in SQL Server can cause performance issues on heap tables because the record outgrows the page and the database engine uses pointers to reference the data. The best practice is to have a clustered index on every table, however, sometimes there are cases when a clustered index is not needed.
2013-07-09
3,188 reads
Blogs
Creating a Striped Backup Set with AI
By Steve Jones
I needed to test a striped backup, so I decided to ask the AI’s...
Trace Flag 1448 – Lessons from a Technical Interview
By gbargsley
In SQL Server environments where transactional replication runs alongside Always On Availability Groups (AGs),...
Disable the sa login in SQL Server (and sleep better)
Disable the sa login in SQL Server (and sleep better)If you run SQL Server...
Forums
Create an HTML Report on the Status of SQL Server Agent Jobs
Comments posted to this topic are about the item Create an HTML Report on...
SQLPS and syspolicy_purge_history job
The SQLPS.exe file has gone AWOL on 2 of my 4 SQL servers, ie,...
Be Wary of Data
Comments posted to this topic are about the item Be Wary of Data
Question of the Day
Locking Hierarchies
You have a table [dbo].[orders] without a Clustered Index (Heap). The table does not have any other nonclustered indexes! You rund the following command in Read Committed Isolation Level:
SELECTo_orderdate,
o_orderkey,
o_custkey,
o_storekey
FROMdbo.orders
WHEREo_orderkey = 3877;