Return to Resume
Function: used for parsing Job Titles to make them consistent per HR standards
View: showing use of Common Table Expression, GROUP BY, and SubQuery
View: showing use of CTE, INNER JOIN, LEFT JOIN, FULL JOIN, CROSS JOIN, and SubQueries
Stored Procedure: showing use of STUFF, FOR XML, PIVOT, and EXEC sp_executesql (Dynamic SQL)
Stored Procedure: used for load New Hires into HR system. Logic built upon CURSOR and multiple nested Dynamic SQL statements with TRY...CATCH.
Stored Procedure: used to merge employee name updates, from HR system into downstream systems. Shows use of IF EXISTS, BEGIN/END TRANSACTION, MERGE, WHEN MATCHED, OUTPUT, and INSERT INTO
SureScripts ePrescribing
SSIS: showing use of C# for SSIS script object used to move files from DMZ.
Copy-Rename Files
PowerShell: Copy-Rename SQL Prompt Snippets to SQL Server Snippets
DMV: Stored Procedure showing use of DMVs in a process that I built and use to help trobleshoot and resolve severe blocking issues.
ShowBadNonClusteredIndexes -- RUNNABLE (copy/paste)
DMV: Use of Dynamic Management Views in T-SQL statement to show possible bad nonclustered indexes based on writes > reads.
MAX() VS TOP 1 .. ORDER BY -- RUNNABLE (copy/paste)
T-SQL: In response to a question raised at the interview, I have created a test case and determined that the correct answer is ... "it depends". The results from my test case show MAX() runs faster when there is no index on the table. When a nonclustered index is created on the dtDate column, the TOP 1 runs faster.
OverPartitionBy -- RUNNABLE (copy/paste)
T-SQL: To follow-up a discussion from the interview, I am providing a situation where the use of the OVER(PARTITION BY ...) function is used instead of the usual GROUP BY to return a SUM value.