2017 Shelby Systems, Inc. Other brand and product names are trademarks or registered trademarks of the respective holders.

Transcription

1 2017 Shelby Systems, Inc. Other brand and product names are trademarks or registered trademarks of the respective holders.

2 The following topics are presented in this session: Database naming conventions for custom programming Script or Stored Procedure Power of stored procedures and optional parameters Common Table Expressions (CTE) instead of sub queries Aggregates, Group By, and Over Clauses Do s and Don'ts for Where and On clauses Cursors: AVOID them when you can. Registering a custom report to work with Arena Lists Best Practices when developing queries Google is your best friend. Database custom programming rules and naming conventions Developer Dos and Don ts Do Not Modify the schema of existing database tables. Any schema changes to the base tables are undone during an upgrade. Modify existing database stored procedures. Any changes to the base stored procedures are overwritten during an upgrade. Modify existing database views. Any changes to the base views are undone during an upgrade. Modify existing database functions. Any changes to the base functions are overwritten during an upgrade. Modify any Shelby Systems Hub packages. Any changes associated with Hub packages are undone when upgrading the Hub package. 1

3 Database custom programming rules and naming conventions Developer Dos and Don ts Do Back up database(s) and create a sandbox database for development. Create new tables following the naming conventions defined in this handout. Create new stored procedures using the naming conventions defined in this handout. Create new functions using the naming conventions defined in this handout. Create new views using the naming conventions defined in this handout. Database custom programming rules and naming conventions DATABASE TABLES Custom database tables should be named as follows: cust_<orgid>_<project ModuleName>_<ClassName> Example: cust_a00000_library_item DATABASE STORED PROCEDURES Custom stored procedures should use either get, save, or del as follows: cust_<orgid>_<project ModuleName>_sp_<action type>_<table name or logical instance> Examples: cust_a00000_library_sp_get_libraryloanbyid, cust_a00000_library_sp_save_libraryloan, cust_a00000_library_sp_del_libraryloan DATABASE VIEWS Custom views should be named as follows: cust_<orgid>_<project ModuleName>_v_<descriptivename> Example: cust_a00000_library_v_library_outstanding_loans 2

4 Script or Stored Procedures? Main advantages of using stored procedures: Stored procedures help promote code reuse. Stored procedures can encapsulate logic on the server. You can modify stored procedures without affecting clients. Optional input parameters make code reuse more possible. In order to use Stored Procedures you need the right development tool(s) to create and maintain them. Two good tools are Visual Studio and SSMS. MY FAVORITE DEVELOPMENT TOOL IS: (SSMS) SQL Server Management Studio. Script developers, take heart; most of the techniques you discuss today also apply to the development of scripts. Power of stored procedures and optional parameters Stored procedure input parameters are optional if you assign a default value to them. That default value is anything, including NULL. What is NULL? NULL is not a value. Null is not zero. NULL is nothing. The NULL value is perfect for use with optional parameters because you use the NULL value to determine if an application passed a value to the stored procedure. Example showing the syntax for a stored procedure with Optional Input Parameters: CREATE PROCEDURE int = NULL,@BirthdayMonth int = NULL.. Body of the stored procedure. 3

5 Power of stored procedures and optional parameters Pretend that you have a requirement for two reports. First report, List all members Name and Birthday. Second report, List every member with a birthday for a given month. Now move to SSMS to see examples of how one stored procedure with optional parameters is used for both reports: 01_cust_A00000_core_sp_get_member_birthday IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[cust_A00000_core_sp_get_member_birthday]') AND type in (N'P', N'PC')) DROP PROCEDURE [dbo].[cust_a00000_core_sp_get_member_birthday] SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON CREATE PROCEDURE int = NULL,@BirthdayMonth int = NULL,@OrganizationID INT = 1 AS /* START OF HEADER COMMENT SECTION TITLE: cust_a00000_core_sp_get_member_birthday AUTHOR: Tim Wilson ORIGINAL DATE: 3/31/2016 REVISION HISTORY: 03/31/2016Tim Wilson New stored procedure for training purposes. DESCRIPTION: Example of a stored procedure with optional parameters. END OF HEADER COMMENT SECTION */ MemberName = coalesce(cp.nick_name, cp.first_name) + ' ' + cp.last_name,birthday = cp.birth_date from core_person cp where cp.organization_id AND(@PersonId is null OR cp.person_id AND(@BirthdayMonth is null OR datepart(month, cp.birth_date) 4

6 Common Table Expressions (CTE) instead of sub queries Common Table Expressions are like a temporary table, sub query, or view. Adding a reference to a CTE in a query is done using the same syntax as referencing a table. Main advantages of using a CTE over sub query: Readability Recursive Queries (Adjacency List) Main advantages of using sub queries Use in populating a column. Use in where clause. When possible, AVOID using sub queries and use CTEs. Sub queries in columns can lead to performance issues. Try moving them to the from clause or use a variable. CTE instead of sub queries Now you move to SSMS to see examples of how to use a recursive CTE to find all the child profile tags associated with a parent profile tag: 02_cust_A00000_core_sp_get_profile_children 5

7 IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[cust_A00000_core_sp_get_profile_children_tags]') AND type in (N'P', N'PC')) DROP PROCEDURE [dbo].[cust_a00000_core_sp_get_profile_children_tags] SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON CREATE PROCEDURE int = NULL,@OrganizationID INT = 1 AS /* START OF HEADER COMMENT SECTION TITLE: cust_a00000_core_sp_get_profile_children_tags AUTHOR: Tim Wilson ORIGINAL DATE: 3/31/2016 REVISION HISTORY: 03/31/2016Tim Wilson New stored procedure for training purposes. DESCRIPTION: Example of a stored procedure using a recursive Common Table Expression. (CTE) END OF HEADER COMMENT SECTION */ with profile_tag_tree as ( tags.profile_id,tags.profile_name,tags.active,profile_hierarchical_name = convert(varchar(max), tags.profile_name),parent_profile_id,anchor_profile_id = tags.profile_id,organization_id,source = cast('anchor' as nvarchar(10)) from core_profile tags where organization_id and ((@AnchorProfileId is NULL and parent_profile_id is null) or (@AnchorProfileId is not NULL and profile_id union all tags.profile_id,tags.profile_name,tags.active,profile_hierarchical_name = convert(varchar(max), profile_tag_tree.profile_hierarchical_name + ' ' + tags.profile_name),tags.parent_profile_id,root_profile_id = profile_tag_tree.anchor_profile_id,tags.organization_id,source = cast('child' as nvarchar(10)) from core_profile tags inner join profile_tag_tree on tags.parent_profile_id = profile_tag_tree.profile_id where tags.organization_id ) profile_id,profile_name,active,profile_hierarchical_name,parent_profile_id,anchor_profile_id,source from profile_tag_tree order by profile_id 6

8 Aggregates, Group By, and Over Clauses Aggregates Aggregate functions perform a calculation on a set of values and return a single value. Group By Clause Works with aggregate functions to perform calculations by combining rows. Over Clause Works with aggregate functions to perform a calculation without combining rows. Aggregates, Group By, and Over Clauses Now move to SSMS to see examples of how to use Aggregates, Group By, and Over Clauses: 03_cust_A00000_core_sp_get_member_cumulative_contribution 7

9 IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[cust_A00000_core_sp_get_member_cumulative_contribution]') AND type in (N'P', N'PC')) DROP PROCEDURE [dbo].[cust_a00000_core_sp_get_member_cumulative_contribution] SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON CREATE PROCEDURE int = NULL,@Year int = NULL,@OrganizationID INT = 1 AS /* START OF HEADER COMMENT SECTION TITLE: cust_a00000_core_sp_get_member_cumulative_contribution AUTHOR: Tim Wilson ORIGINAL DATE: 3/31/2016 REVISION HISTORY: 03/31/2016Tim Wilson New stored procedure for training purposes. DESCRIPTION: Example of a stored procedure using Group By and Over clauses. END OF HEADER COMMENT SECTION */ datetime; ways to correct the Dont issue in a where clause = '1/1/' + cast(@year as nvarchar(4)); = '12/31/' + cast(@year as nvarchar(4)); with grand_totals_by_person as ( cc.person_id,total_contribution = sum(cc.currency_amount),cc.organization_id from ctrb_contribution cc group by cc.person_id, cc.organization_id ) cp.person_id,member_name = coalesce(cp.nick_name, cp.first_name) + ' ' + cp.last_name,cc.contribution_date,cc.currency_amount,cumulative_total = sum(cc.currency_amount) over (partition by cp.person_id order by (cc.contribution_date)),grand_total = gtbp.total_contribution from core_person cp inner join ctrb_contribution cc on cp.person_id = cc.person_id and cp.organization_id = cc.organization_id inner join grand_totals_by_person gtbp on cp.person_id = gtbp.person_id and cp.organization_id = gtbp.organization_id where cp.organization_id and (@PersonId is null OR cp.person_id and (@Year is null or datepart(year, contribution_date) order by cp.person_id, cc.contribution_date; 8

10 Simple Dos and Don'ts for Where and On clauses Dos Use Optional Parameters. Match exact data types exactly. Use aliases for table names. Don t Use nvarchar, varchar, char, or nchar data types for dates (performance/sort issues). Use functions when you can avoid them (columns also). Use sub queries when you can avoid them (column also). Simple Dos and Don'ts for Where and On clauses Now move to SSMS to see examples of Dos and Don ts for Where and On clauses: 04_cust_A00000_core_sp_get_member_info_bad_example And 05_cust_A00000_core_sp_get_member_info_good_example 9

11 IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[cust_A00000_core_sp_get_member_info_bad_example]') AND type in (N'P', N'PC')) DROP PROCEDURE [dbo].[cust_a00000_core_sp_get_member_info_bad_example] SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON CREATE PROCEDURE int = NULL,@BirthdayMonth int = NULL,@Year int = NULL,@OrganizationID int = 1 AS /* START OF HEADER COMMENT SECTION TITLE: cust_a00000_core_sp_get_member_info_bad_example AUTHOR: Tim Wilson ORIGINAL DATE: 3/31/2016 REVISION HISTORY: 03/31/2016Tim WilsonNew stored procedure for training purposes. DESCRIPTION: Example of a stored procedure that reflects bad syntax using sub queries in columns and where clause. The where clause also contains functions that could be reomved. see stored procedure cust_a00000_core_sp_get_member_info_good_example for the proper syntax. END OF HEADER COMMENT SECTION */ with cte caculates total contribution grand_totals_by_person as ( cc.person_id,total_contribution = sum(cc.currency_amount),cc.organization_id from ctrb_contribution cc group by cc.person_id, cc.organization_id ) cp.person_id,title = (select lookup_value from core_lookup where lookup_id = cp.title_luid and organization_id = coalesce(cp.nick_name, cp.first_name) + ' ' + cp.last_name,birthday = cp.birth_date,marital_status = (select lookup_value from core_lookup where lookup_id = cp.marital_status and organization_id = sum(cc.currency_amount) over (partition by cp.person_id order by (cc.contribution_date)),grand_total = gtbp.total_contribution from core_person cp inner join ctrb_contribution cc on cp.person_id = cc.person_id and cp.organization_id = cc.organization_id inner join grand_totals_by_person gtbp on cp.person_id = gtbp.person_id and cp.organization_id = gtbp.organization_id where cp.organization_id and (@PersonId is null OR cp.person_id and (@BirthdayMonth is null OR datepart(month, cp.birth_date) and (@Year is null or datepart(year, contribution_date) and cp.member_status = (select lookup_id from core_lookup where guid = 'B5BD75B0 9FAF 4E28 A956 DD5FD108244C' and organization_id order by cp.person_id, cc.contribution_date; IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[cust_A00000_core_sp_get_member_info_good_example]') AND type in (N'P', N'PC')) DROP PROCEDURE [dbo].[cust_a00000_core_sp_get_member_info_good_example] SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON CREATE PROCEDURE int = NULL,@BirthdayMonth int = NULL,@Year int = NULL,@OrganizationID int = 1 AS /* START OF HEADER COMMENT SECTION TITLE: cust_a00000_core_sp_get_member_info_good_example AUTHOR: Tim Wilson ORIGINAL DATE: 3/31/2016 REVISION HISTORY: 03/31/2016Tim WilsonNew stored procedure for training purposes. 10

12 DESCRIPTION: Example of a stored procedure that reflects best practices. see stored procedure cust_a00000_core_sp_get_member_info_bad_example for example of stored procedure with poor syntax. END OF HEADER COMMENT SECTION */ int = (select lookup_id from core_lookup where guid = 'B5BD75B0 9FAF 4E28 A956 DD5FD108244C' and organization_id datetime = '1/1/' + cast(@year as nvarchar(4)),@yearend datetime = '12/31/' + cast(@year as nvarchar(4)); with cte caculates total contribution grand_totals_by_person as ( cc.person_id,total_contribution = sum(cc.currency_amount),cc.organization_id from ctrb_contribution cc group by cc.person_id, cc.organization_id ) cp.person_id,title = title.lookup_value,member_name = coalesce(cp.nick_name, cp.first_name) + ' ' + cp.last_name,birthday = cp.birth_date,marital_status = ms.lookup_value,cc.contribution_date,cc.currency_amount,cumulative_total = sum(cc.currency_amount) over (partition by cp.person_id order by (cc.contribution_date)),grand_total = gtbp.total_contribution from core_person cp left outer join core_lookup title on cp.title_luid = title.lookup_id and cp.organization_id = title.organization_id left outer join core_lookup ms on cp.marital_status = ms.lookup_id and cp.organization_id = title.organization_id inner join ctrb_contribution cc on cp.person_id = cc.person_id and cp.organization_id = cc.organization_id inner join grand_totals_by_person gtbp on cp.person_id = gtbp.person_id and cp.organization_id = gtbp.organization_id where cp.organization_id and (@PersonId is null OR cp.person_id and (@BirthdayMonth is null OR datepart(month, cp.birth_date) and (@Year is null OR contribution_date and cp.member_status order by cp.person_id, cc.contribution_date; Cursors: AVOID them when you can. SQL Form of Looping Use cautiously and in rare situations. Performance Nightmare!!! 11

13 What is needed to register a custom report to work with Arena Lists? A Stored Procedure/Script must have two parameters spelled and capitalized exactly as as int,,@executionid as int = 0 is not zero, then the report was launched from Arena List. Otherwise, the report was launched from reporting services. Table rept_execution_data contains the person_ids associated with input parameter. What is needed to register a custom report to work with Arena Lists? SSRS Report Builder Report Data Tab Parameters 12

14 What is needed to register a custom report to work with Arena Lists? Now move to SSMS to see examples of how to create a stored procedure report that works with Arena Lists: 06_cust_A00000_core_sp_get_member_info_registered_list IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[cust_A00000_core_sp_get_member_info_registered_list]') AND type in (N'P', N'PC')) DROP PROCEDURE [dbo].[cust_a00000_core_sp_get_member_info_registered_list] SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON CREATE PROCEDURE int,@executionid as int = 0 Allows a report to work with Arena List.,@PersonId int = NULL,@BirthdayMonth int = NULL,@Year int = NULL AS /* START OF HEADER COMMENT SECTION TITLE: cust_a00000_core_sp_get_member_info_registered_list AUTHOR: Tim Wilson ORIGINAL DATE: 3/31/2016 REVISION HISTORY: 03/31/2016Tim Wilson New stored procedure for training purposes. Devrived from cust_a00000_core_sp_get_member_info_good_example to allow it to be a registered report and work with Arena Lists. DESCRIPTION: Example of a stored procedure that reflects best practices. END OF HEADER COMMENT SECTION */ int = (select lookup_id from core_lookup where guid = 'B5BD75B0 9FAF 4E28 A956 DD5FD108244C' and organization_id datetime = '1/1/' + cast(@year as nvarchar(4)),@yearend datetime = '12/31/' + cast(@year as nvarchar(4)); with member_list as ( 13

15 person_id from core_person cp where cp.organization_id and (@ExecutionID = 0) and (@PersonId is null OR cp.person_id union Arena Lists Link. table contains a list of person_ids associated with the creatde Arena list. person_id = data_id from rept_execution_data where execution_id ), grand_totals_by_person as ( cc.person_id,total_contribution = sum(cc.currency_amount),cc.organization_id from ctrb_contribution cc group by cc.person_id, cc.organization_id ) cp.person_id,title = title.lookup_value,member_name = coalesce(cp.nick_name, cp.first_name) + ' ' + cp.last_name,birthday = cp.birth_date,marital_status = ms.lookup_value,cc.contribution_date,cc.currency_amount,cumulative_total = sum(cc.currency_amount) over (partition by cp.person_id order by (cc.contribution_date)),grand_total = gtbp.total_contribution from member_list ml inner join core_person cp on ml.person_id = cp.person_id left outer join core_lookup title on cp.title_luid = title.lookup_id and cp.organization_id = title.organization_id left outer join core_lookup ms on cp.marital_status = ms.lookup_id and cp.organization_id = title.organization_id inner join ctrb_contribution cc on cp.person_id = cc.person_id and cp.organization_id = cc.organization_id inner join grand_totals_by_person gtbp on cp.person_id = gtbp.person_id and cp.organization_id = gtbp.organization_id where cp.organization_id and (@BirthdayMonth is null OR datepart(month, cp.birth_date) and (@Year is null OR contribution_date and cp.member_status order by cp.person_id, cc.contribution_date; Best Practices Best Practices when developing queries: 1. Filter large tables down to smaller data set. Attendance and Contribution tables may contain millions of rows. First CTE should use report parameters to reduce rows. Do not bring in extraneous data (first name, last name, phone number, member status etc.). Only work with IDs. 2. Perform Aggregation on the smaller data set. Use results from the first CTE to perform aggregation on IDs ONLY; avoid large Group By statements. 3. Bring in the Additional Data Final select uses the aggregation CTE and join on other tables using the IDs from the aggregation CTE to bring in the additional data. 14

16 Best Practices cust_a00000_core_sp_get_member_info_good_performance SET STATISTICS IO ON SET STATISTICS TIME ON DBCC FREEPROCCACHE EXEC = NULL,@BirthdayMonth = NULL,@Year = 2016,@OrganizationID = 1 IF EXISTS (SELECT * FROM sys.objectswhere object_id= OBJECT_ID(N'[dbo].[cust_A00000_core_sp_get_member_info_good_performance]') AND type in (N'P', N'PC')) DROP PROCEDURE [dbo].[cust_a00000_core_sp_get_member_info_good_performance] SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON CREATE PROCEDURE int = NULL,@BirthdayMonth int = NULL,@Year int = NULL,@OrganizationID int = 1 AS /* START OF HEADER COMMENT SECTION TITLE: cust_a00000_core_sp_get_member_info_good_performance. AUTHOR: Tim Wilson ORIGINAL DATE: 4/28/2017 REVISION HISTORY: 03/31/2016Tim WilsonNew stored procedure for training purposes. DESCRIPTION: Example of a stored procedure that reflects best practices. END OF HEADER COMMENT SECTION */ INT = (SELECT lookup_id FROM core_lookup WHERE guid = 'B5BD75B0 9FAF 4E28 A956 DD5FD108244C' and organization_id DATETIME = '1/1/' + CAST(@Year as NVARCHAR(4)),@YearEnd DATETIME = '12/31/' + CAST(@Year as NVARCHAR(4)); with cte caculates total contribution filtered_contributions AS (SELECT 15

17 cc.organization_id,cc.person_id,ccf.fund_id,ccf.amount,cc.contribution_date FROM ctrb_contribution cc INNER JOIN dbo.ctrb_contribution_fund ccf ON cc.contribution_id = ccf.contribution_id WHERE (@Year IS NULL OR cc.contribution_date AND cc.organization_id ), grand_totals_by_person AS (SELECT fc.organization_id,fc.person_id,fc.fund_id,total_contribution = SUM(fc.amount) FROM filtered_contributions fc GROUP BY fc.organization_id, fc.person_id, fc.fund_id ), cumlative_totals_by_person AS (SELECT fc.organization_id,fc.person_id,fc.fund_id,fc.contribution_date,cumulative_total = sum(fc.amount) over (partition by fc.organization_id, fc.person_id, fc.fund_id order by (fc.contribution_date)),gtbp.total_contribution FROM filtered_contributions fc INNER JOIN grand_totals_by_person gtbp ON fc.organization_id = gtbp.organization_id AND fc.person_id = gtbp.person_id AND fc.fund_id = gtbp.fund_id ) SELECT cp.person_id,cf.fund_id,cf.fund_name,title = title.lookup_value,member_name = COALESCE(cp.nick_name, cp.first_name) + ' ' + cp.last_name,birthday = cp.birth_date,marital_status = ms.lookup_value,contribution_year FROM core_person cp LEFT OUTER JOIN core_lookup title ON cp.title_luid = title.lookup_id AND cp.organization_id = title.organization_id LEFT OUTER JOIN core_lookup ms ON cp.marital_status = ms.lookup_id AND cp.organization_id = title.organization_id INNER JOIN cumlative_totals_by_person ctbp ON cp.person_id = ctbp.person_id and cp.organization_id = ctbp.organization_id INNER JOIN ctrb_fund cfon ctbp.fund_id = cf.fund_id WHERE cp.organization_id AND (@PersonId is null OR cp.person_id AND (@BirthdayMonth IS NULL OR DATEPART(MONTH, cp.birth_date) AND cp.member_status ORDER BY cp.last_name, COALESCE(cp.nick_name, cp.first_name) 16

18 Best Practices cust_a00000_core_sp_get_member_info_poor_performance SET STATISTICS IO ON SET STATISTICS TIME ON DBCC FREEPROCCACHE EXEC = NULL,@BirthdayMonth = NULL,@Year = 2016,@OrganizationID = 1 IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[cust_A00000_core_sp_get_member_info_poor_performance]') AND type in (N'P', N'PC')) DROP PROCEDURE [dbo].[cust_a00000_core_sp_get_member_info_poor_performance] SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON CREATE PROCEDURE int = NULL,@BirthdayMonth int = NULL,@Year int = NULL,@OrganizationID int = 1 AS /* START OF HEADER COMMENT SECTION TITLE: cust_a00000_core_sp_get_member_info_poor_example AUTHOR: Tim Wilson ORIGINAL DATE: 4/28/2017 REVISION HISTORY: 04/28/2017Tim WilsonNew stored procedure for training purposes. DESCRIPTION: Example of a stored procedure that uses poor programming practices. END OF HEADER COMMENT SECTION */ 17

19 SELECT cp.person_id,cf.fund_id,cf.fund_name,title = title.lookup_value,member_name = COALESCE(cp.nick_name, cp.first_name) + ' ' + cp.last_name,birthday = cp.birth_date,marital_status = ms.lookup_value,contribution_year = sum(ccf.amount) over (partition by cc.organization_id, cc.person_id, ccf.fund_id order by (cc.contribution_date)),grand_total.total_contribution FROM core_person cp LEFT OUTER JOIN core_lookup title ON cp.title_luid = title.lookup_id AND cp.organization_id = title.organization_id LEFT OUTER JOIN core_lookup ms ON cp.marital_status = ms.lookup_id AND cp.organization_id = title.organization_id INNER JOIN ctrb_contribution cc ON cp.person_id = cc.person_id AND cp.organization_id = cc.organization_id INNER JOIN dbo.ctrb_contribution_fund ccf ON cc.contribution_id = ccf.contribution_id INNER JOIN ctrb_fund cfon ccf.fund_id = cf.fund_id INNER JOIN (SELECT cc.organization_id, cc.person_id, ccf.fund_id, total_contribution = SUM(ccf.amount) FROM ctrb_contribution cc INNER JOIN dbo.ctrb_contribution_fund ccf ON cc.contribution_id = ccf.contribution_id WHERE (@Year IS NULL OR cc.contribution_date between '1/1/' + CAST(@Year as NVARCHAR(4)) AND '12/31/' + CAST(@Year as NVARCHAR(4))) GROUP BY cc.organization_id, cc.person_id, ccf.fund_id ) AS grand_total ON cp.organization_id = grand_total.organization_id AND cp.person_id = grand_total.person_id AND ccf.fund_id = grand_total.fund_id WHERE cp.organization_id AND (@PersonId is null OR cp.person_id AND (@BirthdayMonth IS NULL OR DATEPART(MONTH, cp.birth_date) AND cp.member_status = (SELECT lookup_id FROM core_lookup WHERE guid = 'B5BD75B0 9FAF 4E28 A956 DD5FD108244C' and organization_id AND (@Year IS NULL OR cc.contribution_date between '1/1/' + CAST(@Year as NVARCHAR(4)) AND '12/31/' + CAST(@Year as NVARCHAR(4))) ORDER BY cp.last_name, COALESCE(cp.nick_name, cp.first_name) Google IS Your Best Friend. 18

20 Q&A Class Discussion 19

21 Tim is a Software Developer at Shelby Systems and has over 21 years of software development experience with a focus on and passion for database design and development. Tim has a love for Christ and was excited to join the Shelby Systems team in 2014 and use his skills to help develop software solutions for faith based organizations.