Build ETL efficiently (10x) with Minimal Logging

Transcription

1 Build ETL efficiently (10x) with Minimal Logging Simon Cho Blog : Simonsql.com Simon@simonsql.com

2 Agenda Want to discuss first Quick review SARG Index access methods Tipping Point Case 1 What s the best way to pull this table? Introduce for Minimal Logging What is minimal logging? How does it work? Condition Recovery Model

3 Question1 SARG How is it difference? --Query1 BIGINT = 1 SELECT * FROM DBO.[Accounts] WHERE AccountID GO --Query2 BIGINT = 1 SELECT * FROM DBO.[Accounts] WHERE AccountID GO

4 Question1 SARG How is it difference?

5 Question2 SARG How is it difference? --Query1 SELECT AccountID, AccountName FROM DBO.[Accounts] WHERE AccountID = 1000 AccontID : Bigint AccountName : Varchar SELECT AccountID, DCID FROM DBO.[Accounts] WHERE AccountID = '1000' GO --Query2 SELECT AccountID, AccountName FROM DBO.[Accounts] WHERE AccountName = 1000 SELECT AccountID, AccountName FROM DBO.[Accounts] WHERE AccountName = '1000' GO

6 Question2 SARG How is it difference?

7 SARG - Search Arguments Sargability: Why %string% Is Slow string% is it SARG arguments? ble-why-string-is-slow/ CAST and CONVERT (Transact-SQL) Data Type Precedence (Transact-SQL)

8

9 One more question --Query1 SELECT * FROM DBO.[Accounts] WHERE Registered_Datetime > ' ' --Query2 DATETIME = ' ' SELECT * FROM DBO.[Accounts] WHERE Registered_Datetime GO

10 One more question - Cont

11

12 Question 1- Golden Rule Index CREATE TABLE GoldenRuleIndex ( AccountID INT NOT null, Create_Datetime DATETIME NOT null, IsDeleted BIT NOT null, FirstName VARCHAR(255) NOT null, LastName VARCHAR(255) null, Col1 Col10 VARCHAR(255) null ) SELECT * FROM GoldenRuleIndex WHERE Firstname LIKE 'abc%' AND Create_Datetime BETWEEN ' ' AND ' ' AND IsDeleted = 0 Let s assume that, Data is evenly distributed

13 Question 1- Golden Rule Index Which index is SQL server use? SELECT * FROM GoldenRuleIndex WHERE Firstname LIKE 'abc%' AND Create_Datetime BETWEEN ' ' AND ' ' AND IsDeleted = 0 <Index list> nc01 ON GoldenRuleIndex(Firstname,Create_Datetime,IsDeleted) nc02 ON GoldenRuleIndex(Firstname,IsDeleted,Create_Datetime) nc03 ON GoldenRuleIndex(Create_Datetime,Firstname,IsDeleted) nc04 ON GoldenRuleIndex(Create_Datetime,IsDeleted,Firstname) nc05 ON GoldenRuleIndex(IsDeleted,Firstname,Create_Datetime) nc06 ON GoldenRuleIndex(IsDeleted,Create_Datetime,Firstname) Let s assume that, Data is evenly distributed

14 Golden Rule Index SQL server consider Equal sign first. This is the rule of thumb. After that range column. Range column depends on statistics Note: This is rule of thumb. It s not already right. There is a lot of exception. At least, it s not a good idea that Bit column is the leading column of index.

15 Let s talk about Index access methods There are only 3 methods regardless Clustered or Nonclustered (1) Index Scan Execution Plan shows : Table Scan, Index Scan Index Seek Execution Plan shows : Index Seek (2) Individual key look up. (3) Ordered Partial Scan

16 (1) Table Scan/Index Scan SELECT orderid, custid, empid, shipperid, orderdate FROM dbo.orders;

17 (2) Index Seek : Individual key lookup SELECT * FROM [Account].[Accounts] where AccountID in (100,200,300)

18 (3) Index Seek : Ordered Partial Scan SELECT orderid, custid, empid, shipperid, orderdate FROM dbo.orders WHERE orderdate = ' ';

19 Combination Partial Scan + Index Seek SELECT orderid, custid, empid, shipperid, orderdate FROM dbo.orders WHERE orderid BETWEEN 101 AND 120;

20 Let s talk about Index access methods What s the most efficient method for ETL? (1) Index Scan (2) Index Seek - Individual key look up. (3) Index Seek - Ordered Partial Scan Book: Inside Microsoft SQL Server 2005 T-SQL Querying By Itzik Ben-Gan Chapter 3 Must read.

21 Let s talk about Index access methods What s the most efficient method for ETL? (1) Index Scan (2) Index Seek - Individual key look up. (3) Index Seek - Ordered Partial Scan Book: Inside Microsoft SQL Server 2005 T-SQL Querying By Itzik Ben-Gan Chapter 3 Must read.

22 What s the problem of Index Seek? TRUNCATE TABLE #tmp CREATE TABLE #tmp (AccountID BIGINT) GO INSERT INTO #tmp (AccountID) SELECT 1 GO 1000 SELECT a.* FROM [dbo].[accounts] a JOIN #tmp b ON a.accountid = b.accountid It can read same page multiple times!!

23 What s the problem of Index Seek? SELECT a.* FROM dbo.[accounts] a JOIN #tmp b ON a.accountid = b.accountid SELECT a.* FROM dbo.[accounts] a JOIN dbo.num b ON n BETWEEN 1 AND 1000 WHERE AccountID=1 (1000 row(s) affected) Table 'Accounts'. Scan count 0, logical reads 3071, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0. Table '#tmp D'. Scan count 1, logical reads 3, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0. (1 row(s) affected) (1000 row(s) affected) Table 'Num'. Scan count 1, logical reads 6, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0. Table 'Accounts'. Scan count 0, logical reads 3, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0. (1 row(s) affected)

24 What s the problem of Index Seek? SELECT a.* FROM [dbo].[accounts] a JOIN #tmp b ON a.accountid = b.accountid SELECT a.* FROM [dbo].[accounts] a JOIN dbo.num b ON n BETWEEN 1 AND 1000 WHERE a.accountid=1

25 So, what s the Best case for Data Extraction? Using Partial scan instead of individual record seek. What we need for this? Covered + Ordered Index If it s not an option, what should we do? Unordered Scan(Table scan) or Individual seek?

26 Tipping Point That s we call Tipping Point. Ref) Kimberly SQL Pass 2010 : Indexing Strategies It's the point where the number of rows returned is "no longer selective enough". SQL Server chooses NOT to use the nonclustered index to look up the corresponding data rows and instead performs a table scan. What % of data do you guess?

27 Tipping Point Tipping Point Query #1 Table with 1 million rows over 50,000 pages (20 r/p) 12,500 16,666 pages ஃ rows = % Tipping Point Query #2 Table with 1 million rows over 10,000 pages (100 r/p) 2,500 3,333 pages ஃ rows = % Tipping Point Query #3 Table with 1 million rows over 100,000 pages (10 r/p) 25,000 33,333 pages ஃ rows = % Note : This is SQL 2005 testing. And this is not fragmented index. It depend on a lot of things. System, SQL version, Fragmetation and e.t.c. So, No exact number for determine. In my experience, generally greater than 1% of data, Table Scan is better.

28 Tipping Point What s exactly it s affected? Directly affected Index Seek vs Scan for data driven. Book mark lookup or Cluster scan. Indirectly related for ETL pull whole data vs just Delta data. Need to consider write as well. We can utilize minimal logging. Update bulk records or Create new table. Generally 5-10% data change is the Tipping point for ETL. About 20% data change, rebuild is better most likely.

29 Case 1 Source Table(Source_A) 1.5 GB table 20 M records Target Table(Target_B) 1 Clustered Index + 3 NonClustered Indexes Daily Base Goal Daily base refresh Target Table. Pull data using Linked Server

30 Case 1 Which method? Method 1 Drop clustered index Drop all nonclustered indexes Truncate table Target_B Insert Target_B select * from Source_A Create clustered index Method 2 Drop Table Target_B Create table Target_B Create clustered index Create all nonclustered index Insert Target_B select * from Source_A Method 3 Simple is the best! Truncate table Target_B Insert Target_B select * from Source_A Create all nonclustered indexes Or I have better one(?)

31 Case 1 Which method? Method 4 Truncate table Drop all Nonclustered Indexes Drop Clustered Index Insert Target_B with(tablock) Select * from Source_A Create Clustered Index Create all Nonclustered Indexes Method 6 Drop Table Target_B Select * into Target_B from Source_A Create Clustered Index Create all Nonclustered Indexes Method 5 Truncate table Drop all Nonclustered Indexes. Cluster index remains Insert Target_B with(tablock) Select * from Source_A Create all Nonclustered Indexes

32 Scenario 1 Summary 1 Million = 80 MB, SSD, Linked Server Recovery Method Seconds Log Count Log Length(Bytes) Compare Simple Times Simple 2, Times Simple 4,5, Bulk Times Bulk 2, Times Bulk 4,5, Full Times Full 2, Times Full 4,5, Times Note : How to check Log count and Log Length 1. CHECKPOINT or Log backup depends on Recovery mode 2. Execute below statement. SELECT COUNT(*) AS LogRecordCount, SUM([Log Record Length]) FROM sys.fn_dblog(null,null)

33 Maybe someone say like this!

34 Somebody say my test is wrong. SSIS is super fast!!. Do not use linked server! So, I tested it method 3 with SSIS package. Recovery Metho d Seconds Log Count Log Length(Bytes) Compare Simple Times Bulk Times Full Times Nothing Difference!!

35 Somebody say Duration Doesn t differ So, we are ok to use old method. Yes, I m quite impressed with SSD. So that, I tested with USB external disk. 20 Million, 1.5 GB. Only for slowest(method3) and fastest(method4) Recovery Method Secon ds Log Count Log Length(Bytes) Compare Simple Times Simple Still impressive. Duration doesn t that much differ. (I expected about 20 times difference) But, I m pretty sure, if you dealing with bigger size of data, You will see a lot difference. Ex) In my experience, 24 hours big ETL job, only takes 45 Min.

36 Let s look at detail number(20 M, 1.5 GB) 1,005,690 writes(physical write) * 8Kb/1024/1024 = 7.9 GB reads(physical read) * 8Kb/1024/1024 = 5.5 GB 1,298,861 CPU_Time /1000 = 1,298 Sec 554,488,821 Logical_reads(Buffer pool read) * 8Kb/1024/1024 = 4230 GB Just for 1.5 GB Table!! 8 Times more log created on Disk VS 6 Times CPU, 1.5 times reads, 2 times writes, 250 times Buffer pool read

37 I know you feel like this

38 Minimal Logging Operation Full Logging Operation Everything logged by each row level. Minimal Logging Operation Someone call No-Logging. Technically not true. Do not log every individual row change. Only logging enough rollback information. Only logs extent allocations each time a new extent is allocated to the table. Minimal Logging Prerequisites For a database under the full recovery model, all row-insert operations that are performed by bulk import are fully logged in the transaction log. Note : After SQL2008 it s improved with TabLock After 2008 and Above in Full recovery mode It s logging by Page allocation level. CDC or Replication - Always fully logged.

39 What can be minimally logged With Prerequisites Below operation can be minimally logged Select Into Bulk Import, Bulk Insert, Bcp Create/Alter/Drop Index Insert into Table with (TabLock) select

40 Do you concern with Table Lock? Minimal logging is required Table Lock during inserting data. Table Lock Basically, it ll blocking other update/insert operation. Read committed can t read data either. Dirty read(nolock) is ok to read. So, not a many developer like blocking. * Select * into : Schema Modification lock is occurred. Do not allow dirty read either.

41 Do you concern with TabLock? This is SSIS Package is default setting. Data Flow Destination

42 Prerequisites of Minimal logging # Table Requirements for Minimally Logging Bulk-Import Operations The table is not being replicated. Table locking is specified (using TABLOCK) Database Recovery : Bulk-logged or Simple Note: The bulk-logged recovery model is designed to temporarily replace the full recovery model during large bulk operations No indexes (Heap). Don t care empty or not : data pages are minimally logged. Nonclustered indexes only : data pages are minimally logged. If the table is empty, index pages are minimally logged as well If table is non-empty, index pages are fully logged. Ex) If you start with an empty table and bulk import the data in multiple batches, both index and data pages are minimally logged for the first batch, but beginning with the second batch, only data pages are minimally logged. Clustered Index, No Nonclustered index, and empty table : both data and index pages are minimally logged. If a table is non-empty, data pages and index pages are both fully logged. EX) If you start with an empty table and bulk import the data in batches, both index and data pages are minimally logged for the first batch, but from the second batch onwards, only data pages are bulk logged. Clustered Index and NonClustered index : Fully logged.

43 (1) If you are using the INSERT SELECT method, the ORDER hint does not have to be specified, but the rows must be in the same order as the clustered index. If using BULK INSERT the order hint must be used. (2) Concurrent loads only possible under certain conditions. See Bulk Loading with the Indexes in Place. Also, only rows written to newly allocated pages are minimally logged. (3) Depending on the plan chosen by the optimizer, the nonclustered index on the table may either be fully- or minimally logged. Minimal Logging Operation Indexes Rows in table Hints Logging Heap Any TABLOCK Minimal Heap Any None Full Heap + Index Any TABLOCK Full Cluster Empty TABLOCK, ORDER (1) Cluster Empty None Full Cluster Any None Full Cluster Any TABLOCK Full Cluster + Index Any None Full Cluster + Index Any TABLOCK Full Minimal

44 What is Recovery Mode? Full Log backup required Full logging everything Note : Starting SQL 2008, some statement can be small logged even in full recovery mode. Simple Automatically reclaims log space. No log backup Log chain is broken Not able to restore Point-in-time Fully Support minimal logging operation Bulk_Logged Log backup required Note : The log size pretty much same as full recovery mode even the minimal logging operation. Fully Support minimal logging operation Log chain is NOT broken. Note : Unfortunately, Mirrored database can t changed

45 Bulk Recovery Mode Protects against media failure. Normal transaction(full logging Transaction) Same as Full recovery mode. Minimal logging operation Provides the best performance and least log space usage. LDF file doesn t have full traction log. Point-in-time is NOT available.(stopat doesn t allow) Log backup is contain whole page(extent) data. Please check below URL before change Bulk recovery mode.

46 Bulk Recovery Mode - Cont There is risk. But, performance gain is very big. And it s required only Target DB. Ex) how to use Temporary change to Bulk recovery mode for Minimal logging STMT in Full logging Database. Run the log backup more frequently. Change back after minimal logging operation.

47 No way to ML existing table!! Based on the Prerequisites chart. Only 2 cases do minimally logged. Heap (Don t care data. No NCindex) Clustered (Empty. No NCindex) Table Lock required Bulk or Simple recovery required.

48 It was Soooo frustrated!!

49 Introduce about Trace Flag 610 SQL 2008 and above When the bulk load operation causes a new page to be allocated, all of the rows sequentially filling that new page are minimally logged. Please don t enable this TF on Prod right away. It may make overhead for regular full logging transaction.

50 Minimal Logging Operation-TF610 Table Indexes Rows in table Hints Without TF 610 With TF 610 Concurrent possible Heap Any TABLOCK Minimal Minimal Yes Heap Any None Full Full Yes Heap + Index Any TABLOCK Full Depends (3) No Cluster Empty TABLOCK, ORDER (1) Minimal Minimal No Cluster Empty None Full Minimal Yes (2) Cluster Any None Full Minimal Yes (2) Cluster Any TABLOCK Full Minimal No Cluster + Index Any None Full Depends (3) Yes (2) Cluster + Index Any TABLOCK Full Depends (3) No

51 Q & A Simon Cho Blog : Simonsql.com Simon@simonsql.com