1. Ridewaan Hanslo ridewaanhanslo
MS SQL SERVER: Re-engineering legacy SQL Server Radius Accounting Processor Archiving solution.
Ridewaan Hanslo
ridewaanhanslo

2. Thank You Sponsors

3. Overview Problem Statement Optimization Archiving Configuration
Monitoring
Scaling/Availability
Demo (Code)

4. Problem Statement

5. ISSUES IDENTIFIED Issue 1: SPROC’s for archiving.
Issue 2: Lack or bad indexing.
Issue 3: Table Reads/Writes configuration.
Issue 4: Badly configured Agent Jobs.
Issue 5: Lack of Monitoring/Validation.
Issue 6: Lack of Documentation.

6. Optimization

7. INDEXES
Add/Remove/Update Indexes on the tables that forms part of the processing.
Add indexes – prevent unnecessary full table scan/heaped approach.
Remove indexes – saved 60GB of HDD space.
sp_BlitzIndex

8. Indexes (continued…)

9. Indexes (continued…)
* To be deprecated

10. Tables
Optimised tables mostly used for querying purposes as reading tables (faster reads).
Optimized tables mostly used for writing to purposes as write tables (faster writes).

11. Tables (continued…)

12. Archiving

13. ARCHIVING (continued…)
Old Way - raw selects (no caching), to gather data and looping through them slowly causing frequent crashes of the archiving jobs.
New Way – Cached-Incremental Data Load method was used with the SSIS packages.

14. ARCHIVING (continued…)
The Project has 2 project sets.
SQL Server 2012
SQL Server 2014

15. ARCHIVING (continued…)

16. ARCHIVING (continued…)

17. CONFIGURATION

18. SSIS CATALOG
Publish packages to the Server

19. SQL AGENT JOBS Usage Processing – runs every 4 mins. Job 2:
Archiving – runs once a month.

20. Monitoring

21. Monitoring Monitor 1: SQL Agent Job – Execution Date Monitor 2:
SQL log history.
Monitor 3:
Notifications.
Monitor 4:
Live/Staging Tables.

22. SCALING & Availability

23. SCALING & Availability
Vertical Scaling
Horizontal Scaling
e.g. Table partitions
Availability
e.g. Database Mirroring

24. Demo (CODE)

25. REFERENCES
[1]

26. Questions
Thank you!