2020-07-03
536 reads
2020-07-03
536 reads
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
By Steve Jones
I needed to test a striped backup, so I decided to ask the AI’s...
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)If you run SQL Server...
Comments posted to this topic are about the item Create an HTML Report on...
The SQLPS.exe file has gone AWOL on 2 of my 4 SQL servers, ie,...
Comments posted to this topic are about the item Be Wary of Data
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;